4 ms·
Perhaps I'm misunderstanding, but the article claims the "code" is unencrypted, and that seems a little misleading. Apple hasn't encrypted the binary, but they
by jlarocco 10y ago
Perhaps I'm misunderstanding, but the article claims the "code" is unencrypted, and that seems a little misleading. Apple hasn't encrypted the binary, but they're not really shipping the source, right?
- Titanous 10y agoCorrect, the executable code is unencrypted, the source code has not been released.
- xxr 10y agoDoes this mean that all the NSWhatever symbols are visible to anyone with a debugger or readelf or whatnot?
- umanwizard 10y agoWell you already have the symbols; what else would your app be linking against? If you mean the functions themselves, not the symbols -- those are in the dyld cache[1], not the kernel. It's unclear from this article how easy it will be to dump the dyld cache in iOS 10. [1]: http://iphonedevwiki.net/index.php/Dyld_shared_cache http://iphonedevwiki.net/index.php/Dyld_shared_cache
- asksol 10y agoEdit: Ignorance is bliss
- umanwizard 10y agoYou're thinking of debugging symbols -- the commenter I replied to mentioned symbols in general. Linkers rely on names and addresses; more precisely, name->address mappings.