2 ms·
Those are just a few examples, the surface area is obviously massive (100s if not 1000s). We both know that. The reality is that iOS was not designed with this
by CyberRabbi 6y ago
Those are just a few examples, the surface area is obviously massive (100s if not 1000s). We both know that. The reality is that iOS was not designed with this attack vector in mind. Here is yet another one I just randomly thought up “install date of app” https://stackoverflow.com/questions/39255403/get-date-of-when-app-was-installed-ios https://stackoverflow.com/questions/39255403/get-date-of-whe... now imagine what a dedicated developer could design.
- tinus_hn 6y agoSorry, it’s not difficult or forbidden to remember user identity in your own app. It’s about sharing that identity between apps. And by the way, there is absolutely nothing stopping Apple from reporting your app was installed on January 1st, 1970.
- CyberRabbi 6y ago> And by the way, there is absolutely nothing stopping Apple from reporting your app was installed on January 1st, 1970. I doubt Apple would do that but I think you are very much missing the point. These one-off patches are not effective at scale, there are literally 100s if not 1000s of information leaks of this type that indeed are observable across multiple apps. App install date was just one that I pulled from thin air that required no thought. A dedicated engineer could easily solve this problem.