- This breaks DNS resolution for company-internal domains.
- This routes all my traffic through CloudFlare or another CDN I might or might not trust (yes, the IP is hidden, but not the data)
- it significantly slows down my internet access on my location.
- it tends to turn itself on again without my intervention
especially the last point is very problematic for me
The fact they can see unencrypted HTTP data is a downside with all VPNs. At least you have the double hop going in your favor.
As for turning on by itself, it’s annoying, but it is the very first developer-only preview so I’m not complaining yet.
Is this not the case for any VPN or proxying service? In fact, it could even be a security flaw if your internal domains were accessible on external VPN style endpoints?
There’s value in talking about issues early as it allows admins of corporate networks to make adjustments to their infrastructure (like introducing split dns rather than just have *.internal.example.com resolve to internal addresses) to be prepared for the eventual launch of this feature in September
No, it's not.
> In fact, it could even be a security flaw if your internal domains were accessible on external VPN style endpoints?
It would be, but then this is not something that happens on a network configured in the way you describe.
I’m not sure what kind of network you believe I described, but would be useful to have a clearer explanation from you.
The root's observation is that it doesn't use the machine configured DNS. The overwhelming majority of VPNs also don't use the machine configured DNS. Maybe not "any", but if you're using a VPN you're generally going to want your DNS going over it as well.
But it is worth noting if you're on a corporate network, or if you use a DNS solution like NextDNS -- when you turn on PR those no longer play a part, at least to Safari traffic.
Using TLS it certainly should be.
Because if it is instead actually unwrapping the connection somehow (eg. mitm) then they would be able to see the content, and that seems like a huge no-go -- both for the users, AND for apple as I would think it would open them up to liability.
note: they certainly would be able to see unencrypted http traffic regardless though.
Why would it? The WWDC developer video clearly states that it’s only for public domains.
Isn't the great majority of your traffic HTTPS?
And to answer the original guy, no Apple does not add any headers or details to tell the destination what your IP address is. They just see that they're talking to an exit node somewhere approximal of your general region.
I turned it on and actually forgot I did. Performance is decent here. I mean of course it's going to be worse than native, but that's the compromise.
As to trusting Cloudflare -- what do you mean? You understand your connection is still TLS end-to-end encrypted (presuming that's what we're talking about), right? I mean...presuming the site your talking to isn't using Cloudflare SSL. In no way does this reduce that security. If you're talking about HTTP, well everyone in between can already see that.
Why is it so clear? An iPhone hotspot turns itself off as soon as a device disconnects, with no option to leave it on, presumably for security or battery reasons.
Funny story, I was shocked and quite annoyed that an iPhone automatically turns on Wifi and stuff every day by itself - even if you turn it off...
Still dont know how to actually turn it off
Which makes it pretty clear it’s not a wifi kill switch but just a “my current connection is shit, let me use cellular” button.
it’s not quite as egregious, but it reminds me of how a lot of desktop apps now just minimise to tray rather than actually ending the process when you click the close button. discord is probably the worst offender for that, since it’s not (that I’m aware) a customisable behaviour
Settings > app settings - Window settings > close button - minimize to tray.
Turning this off causes Discord to quit completely when clicking the red X in the top right.
Apple gains nothing from your WiFi re-engaging. But many users do because, as another comment mentioned, people turn it off in control center because their connection is temporarily shit, or more likely just accidentally. Then they get to end of month and they have a monster cell overage.
Someone was using control center wrong (despite it very clearly indicating the use of the button). It's a learning experience.
No, I'm not wrong. I'm actually completely right. Control Center has always been a temporary toggle.
In case you’re just entirely misunderstanding what we’re talking about, I’m referring to being able to turn off the wifi when you swipe up from the bottom of the screen. This has been a feature since I’ve used an apple device, which is since iOS 5 or 6. Whether it’s been called “control centre” or not is irrelevant. That’s not even what I referred to it as in my first comment.
If you disable it from settings, it stays off.
Of course I’m talking about the beta version. But I can assure you that once I found out that it interferes with internal DNS, I turned it off (it’s on by default on the current betas) and a day later it was back on.
That’s what I meant with „it turns itself on again“