Apple ignores VPN bug in iOS for months

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


Well-known member
Nov 1, 2020
An interesting read from ProtonVPN. Basically, when an iOS VPN kicks in, it does not corral all existing threads/sockets/connections. I have seen this in other VPN contexts too. If you have a professional grade router, you should be able to monitor/log any new outgoing connection that is not destined for the VPN server.
Its one thing to have a bug, and quite another thing to ignore it for months.
There are pro's and cons to killing all current connections where connecting to the VPN. Many applications don't handle this very well. Slack for instance takes many minutes before it realizes that the connection it had established is no longer valid, so no new messages show up and all slack calls are dropped. Thankfully zoom almost doesn't miss a beat. But Slack is hardly alone, SSH, and file transfers both break if you connect to a VPN.

Of course there are privacy/security implications of current connections not using the VPN, but for my usage, where I need to use a VPN tp access certain resources, but find it too slow to leave it on all the time, I like the current implementation.
TL;dr: if you're bothered, turn on VPN, then turn on Airplane Mode, pause, turn off Airplane Mode.

I wonder where the CVE for this "vulnerability" is. ProtonVPN blog says Apple addressed the issue in mid-October, but apparently not to ProtonVPN's liking. I don't hear much outrage about this elsewhere.

Turns out ProtonVPN started banging a drum about this is 13.4, last spring. Sophos has, what looks like a good analysis.

@Steve just noted on SN794, Firefox had to step back from encypting all DNS traffic for valid enterprise network concerns. I wonder whether this vpn issue is related to enterprise users.