4 ms·
Facebook’s shady coding in the past was all using sanctioned APIs, including the VPN it was using to spy on teens. With a private store also goes the static ana
by LeoNatan25 3y ago
Facebook’s shady coding in the past was all using sanctioned APIs, including the VPN it was using to spy on teens. With a private store also goes the static analysis of private API usage, which can enable software some looser restrictions (but not much, as some fear—most stuff is protected for at the kernel level).
- Apocryphon 3y agoMaybe static analysis can be imposed at the OS level, like macOS notarization? https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution https://developer.apple.com/documentation/security/notarizin... I don't think the regulators are going to mandate that Apple not retain any consumer-protecting mechanisms.
- LeoNatan25 3y agoSee my comment here: https://news.ycombinator.com/item?id=37667740 https://news.ycombinator.com/item?id=37667740 Static analysis is very easy to be fooled. iOS security comes from its kernel enforcement by means of entitlements, which you can’t easily break.
- Apocryphon 3y agoGiven that it’s already present in App Store apps as you say would show that the App Store itself, and perhaps the current app review process, is insufficient!
- LeoNatan25 3y agoI don’t know. It’s a cat and mouse game, and you can only win in such games if you don’t play. By moving the security from static analysis to kernel, Apple has sidestepped most malicious API mishaps. My project isn’t malicious, it just uses API not as intended, but it can do little malice in wrong hands. I think this is a good system overall.