5 ms·
> which would allow developers to cause all sorts of unchecked havoc. This is simply not true. The security boundary is not at that layer. Calling private meth
by ianlevesque 3y ago
> which would allow developers to cause all sorts of unchecked havoc.
This is simply not true. The security boundary is not at that layer. Calling private methods doesn't escape the sandbox.
- judge2020 3y agoSure, but private methods are another vector - tracking and bypassing the IDFA and potentially acting as official Apple Apps to use/abuse things like Carrier/SIM info[0], updating the wallpaper for the user[1], accessing call history[2], etc. 0: https://github.com/nst/iOS-Runtime-Headers/blob/fbb634c78269b0169efdead80955ba64eaaa2f21/Frameworks/CoreTelephony.framework/CTMobileEquipmentInfo.h#L10 https://github.com/nst/iOS-Runtime-Headers/blob/fbb634c78269... 1: https://github.com/nst/iOS-Runtime-Headers/issues/32 https://github.com/nst/iOS-Runtime-Headers/issues/32 2: https://github.com/nst/iOS-Runtime-Headers/tree/fbb634c78269b0169efdead80955ba64eaaa2f21/PrivateFrameworks/CallHistory.framework https://github.com/nst/iOS-Runtime-Headers/tree/fbb634c78269...
- saagarjha 3y agoThese are all security issues that Apple fixes by moving them outside of the process.