3 ms·
Right, but isn’t the issue then “I can trick a system service to do the malicious thing for me”? Apple’s apps are absolutely not secured against being convinced
by saagarjha 6y ago
Right, but isn’t the issue then “I can trick a system service to do the malicious thing for me”? Apple’s apps are absolutely not secured against being convinced to make arbitrary outbound connections.
- coldtea 6y ago>Apple’s apps are absolutely not secured against being convinced to make arbitrary outbound connections. Aren't they? They're signed, notarized, sandboxed, have ASLR, and other protections, in Big Sur they even recide on a read-only partition iirc...
- sneak 6y agoThere are a million other ways to “convince” them when they are operating normally, which presumably these apps are not explicitly hardened/audited against.
- saagarjha 6y agoI am very familiar with macOS's security features. Preventing an application from having something maliciously command them into sending things on the network is not one of the threat models Apple considers (or at least, they have no specific mitigations against this). As a simple (but conspicuous) example, consider an app simply opening a customized HTTP link if Safari was exempt from the firewall to exfiltrate information. There are hundreds of ways to do effectively the same thing more surreptitiously.
- Someone 6y ago“I can trick a system service to do the malicious thing for me if I have root”, and that’s as designed, and something at least people on HN want (“I want control over what my hardware runs”) If you have root, you can also remove Apple’s exceptions from that list. I haven’t checked, but that should fix the issue of Apple’s services bypassing firewalls.