3 ms·

> macOS Big Sur deliberately cripples VPN and firewall on it so that select Apple softwares can bypass them That was debunked: https://www.reddit.com/r/mac/com

by messe 6y ago

> macOS Big Sur deliberately cripples VPN and firewall on it so that select Apple softwares can bypass them That was debunked: https://www.reddit.com/r/mac/comments/k0c00f/macos_big_sur_does_not_bypass_vpns/ https://www.reddit.com/r/mac/comments/k0c00f/macos_big_sur_d...

politelemon 6y ago
Read the thread carefully. The vpn part was shown to be normal, not the firewall. The original problem was with the firewall, there were only passing mentions of the vpn which op tested. Also problematic, the op released no data. Whether that works for you depends on your pov.
- duskwuff 6y ago
  The "firewall" was Little Snitch -- which was implemented using a framework intended for per-application VPNs.
  - webmobdev 6y ago
    Not just "Little Snitch", all Firewalls that had their own kernel extensions. With macOS Big Sur, Apple started insisting that thry have built specific API's for firewall softwares, and every firewall app had to use only that, and their custom kernel extensions won't be allowed. But Apple's API are ofcourse designed to allow it bypass their whitelisted softwares. More here: https://medium.com/tripmode/apple-started-hiding-the-traffic-of-its-own-mac-apps-9dc83c5a9c5b https://medium.com/tripmode/apple-started-hiding-the-traffic...
heyoni 6y ago
It bypasses firewalls, or network blockers using the new APIs...not sure how the vpn thing got started because that was never part of the original claims.
- webmobdev 6y ago
  > not sure how the vpn thing got started Some VPN apps use their own kernel extension and macOS Big Sur discourages that. https://tunnelblick.net/cTunTapConnections.html https://tunnelblick.net/cTunTapConnections.html Some VPN apps that weren't using VPN but used proxying also are affected. Also read https://protonvpn.com/blog/big-sur-exclusion-list/ https://protonvpn.com/blog/big-sur-exclusion-list/ for more info.

by messe 6y ago

politelemon 6y ago

Read the thread carefully. The vpn part was shown to be normal, not the firewall. The original problem was with the firewall, there were only passing mentions of the vpn which op tested. Also problematic, the op released no data. Whether that works for you depends on your pov.

duskwuff 6y ago
The "firewall" was Little Snitch -- which was implemented using a framework intended for per-application VPNs.
- webmobdev 6y ago
  Not just "Little Snitch", all Firewalls that had their own kernel extensions. With macOS Big Sur, Apple started insisting that thry have built specific API's for firewall softwares, and every firewall app had to use only that, and their custom kernel extensions won't be allowed. But Apple's API are ofcourse designed to allow it bypass their whitelisted softwares. More here: https://medium.com/tripmode/apple-started-hiding-the-traffic-of-its-own-mac-apps-9dc83c5a9c5b https://medium.com/tripmode/apple-started-hiding-the-traffic...

heyoni 6y ago

It bypasses firewalls, or network blockers using the new APIs...not sure how the vpn thing got started because that was never part of the original claims.

webmobdev 6y ago
> not sure how the vpn thing got started Some VPN apps use their own kernel extension and macOS Big Sur discourages that. https://tunnelblick.net/cTunTapConnections.html https://tunnelblick.net/cTunTapConnections.html Some VPN apps that weren't using VPN but used proxying also are affected. Also read https://protonvpn.com/blog/big-sur-exclusion-list/ https://protonvpn.com/blog/big-sur-exclusion-list/ for more info.