I guess fixing the leak must be detrimental to Apple in some way so it won’t get fixed until Apple can resolve that, but based on the how long this has been going on, they probably can’t.
Based on what is said in the article, this may be a workaround to make sure all connections go through VPN.I read somewhere that if you enable VPN, then toggle Airplane Mode On then Off, existing connections will be dropped and then reconnected via VPN. Of course the VPN needs to establish a connection before anything else. I've no idea if that is 100% guaranteed though.
I think this bug means you can't trust that one either... That's the point here-- when you enable VPN you expect your traffic to go through it, and this says some traffic leaks around it.The only VPN I trust is one I set up myself....
While true regarding not being bulletproof, it's not clear to me if the problem is not wanting to affect user experience or simply not fixing a glaring bug.VPNs aren't bulletproof, but these are negligent oversights. I'm guessing Apple doesn't want to make the. necessary changes to iOS that may adversely affect the user experience, such as killing all existing sessions (which could result in the user being challenged for credentials repeatedly).
I disagree with this. If I remember the history correctly, Apple pulled all the VPN hooks under their control because it was being abused, particularly by unscrupulous "ad blockers". They've put an enormous amount of effort into their various efforts to prevent tracking, prevent browser fingerprinting, private relay, secure ad blocking, etc, etc. You don't put that kind of effort into a whitewash.The truth is, Apple is more concerned with the appearance of privacy rather than actually protecting its customers.
Still better than whatever Android's flavor of the month is.
They need it for their upcoming Ad Network.I guess fixing the leak must be detrimental to Apple in some way so it won’t get fixed until Apple can resolve that, but based on the how long this has been going on, they probably can’t.
Researchers like this count on the “Hate Apple” crowd to:While this is certainly troubling and I hope they address it, if all that is “leaking” is health, maps, and wallet then I’m not too concerned. Health is already end to end encrypted meaning apple can’t read it. Wallet (as it pertains to purchases) is end to end encrypted meaning apple can’t read it. Maps, sure. That should be patched.
I’d be worried if safari data was dns leaking. That would be a major security flaw.
This is essentially the mindset I think the developers had here to begin with. It's a totally legitimate reason for a VPN client to simply connect securely to an office or home network from outside, so the device behaves like it's on that local network while tunneling in.vpn is no privacy tool, it is for connecting 2 networks secure. Don't try to change a feature to do a thing it is not meant to do...
Not slow, careless. Apple’s software quality lately is just shocking.I don’t know anything about modern software design … but is this a hard problem to solve in iOS or is apple just being slow (or both)?
If it's for connecting two networks securely, surely you will agree that having some data escaping being securely transmitted between those two networks is a problem, right?vpn is no privacy tool, it is for connecting 2 networks secure. Don't try to change a feature to do a thing it is not meant to do...
Doesn’t matter what it was originally intended to do. This is what it has become and people expect it to be.vpn is no privacy tool, it is for connecting 2 networks secure. Don't try to change a feature to do a thing it is not meant to do...
Are they? It's my world too and I have never seen a split tunnel setup. What we use VPN for is accessing secured resources in house from remote users. It's nice to be able to encrypt all data to and from so any older protocols that we do need to use (legacy stuff), are basically unseen by anyone else. Ours is a full tunnel with the stipulation you don't attach if the client is requesting a split tunnel. It wouldn't be secure enough as a split tunnel traffic could be sniffed too easily from outside.Most use cases are split tunnel in the corp world.
Perfect, they just care about your $$$. /sApple doesn’t care about your security.
This is exactly why many people give up on providing feedbacks through “official channel“ directly, instead gambling on blowing up the issue in the media so media could collectively report issue to Apple by making louder noises.there's simply no way to give feedback to someone who actually has the power to do something about it.
It behooves these “researchers” that you don’t think about what’s actually happening. Because, if they mentioned anything about what real level of concern folks would have, nowhere near as many folks would be talking about it.Can anyone provide a reasonable description of and explanation for what exactly is "leaking" and why this is a problem? This is a serious question. The discussion of the issue back in August was mostly people catastrophizing over the "leaks" but I didn't read anything that clearly explained what the risks were. So far the discussion here has also mostly been catastrophizing and criticism without explanation of why it's an issue.
Considering this has been a “thing” for years, and it has blown up previously, at this point it’ll just blow up over and over again every time a Security Researcher needs to get their name in the news.This is exactly why many people give up on providing feedbacks through “official channel“ directly, instead gambling on blowing up the issue in the media so media could collectively report issue to Apple by making louder noises.