3 ms·
It would seem the solution is to require every 'unarchive' operation to provide a 'schema' which specifies exactly which classes will be used in the unarchive o
by londons_explore 5y ago
It would seem the solution is to require every 'unarchive' operation to provide a 'schema' which specifies exactly which classes will be used in the unarchive operation. That schema would be read-only and specific to the unarchive call site.
- valleyer 5y agoYou're sort of describing NSSecureCoding. Unfortunately, it's not used everywhere, and (because Cocoa relies heavily on internal class clusters) it still allows subclasses of the specified class.
- olliej 5y agoI also recall one exploit that happened despite using nssecurecoding because a special internal class was a subclass of a secure coding class