2 ms·
This exploit, like many before it, make use of NSKeyedUnarchiver. It's a class which allows arbitrary types to be serialized on the wire. I think it's time th
by londons_explore 7y ago
This exploit, like many before it, make use of NSKeyedUnarchiver.
It's a class which allows arbitrary types to be serialized on the wire.
I think it's time that Apple had a new policy that no NSKeyedUnarchiver will ever go from one iPhone to another. They could do that by having a random 64 bit number in the header, and if the header doesn't match the local device, refuse to unarchive.
Then all software that breaks, find new ways to encode the specific data they need to send over the wire. Specifically, require they send a specific serialized class structure (ie. something with a schema), rather than something general purpose.
- deleted 7y ago[deleted]
- izacus 7y agoUsing NSKeyedUnarchiver (and other language serializers) on the wire is also a great way to make sure your product is going to be extremely hard to port to other platforms. Even the plist version is not easy to handle outside Apple world. I've consulted many companies which found out that they need to expand beyond Apple horizons, just to find out that their whole infrastructure is based on Apple's binary formats which aren't well documented and are not easily (and reliably) readable on other platforms. Pragmatic move in these cases is to use formats that aren't platform dependent - things like JSONs, Cap'n Proto, msgpack and others.
- saagarjha 7y ago> your product is going to be extremely hard to port to other platforms I'm sure this isn't a particularly troubling issue for Apple.
- londons_explore 7y agoIm sure they'd like the ability to port a service like iMessage to Android, just to give them options incase a big competitor starts eating their user base with cross platform support.
- saagarjha 7y agoApple could just build their frameworks for other platforms–they've done it before.