I’m surprised this code isn’t being rewritten in something like Rust, but perhaps there are more things going on at play, like the plist serialization attacks that end up coding for esoteric classes that contained various bugs.
I’m surprised this code isn’t being rewritten in something like Rust, but perhaps there are more things going on at play, like the plist serialization attacks that end up coding for esoteric classes that contained various bugs.
[1] https://habr.com/ru/post/191654/
[2] https://appleinsider.com/articles/15/05/27/bug-in-ios-notifi...
[3] https://blog.zecops.com/research/analyzing-the-ios-telugu-cr...
[4] https://www.macrumors.com/2018/05/09/how-to-fix-black-dot-im...
I imagine the internal discussion is something like "by rewriting it, we will just introduce 100 new bugs. once we squash these last few bugs in the current tried-and-tested C code, it will be bulletproof!"
Being Apple I imagine they would prefer to rewrite it in Swift, but Swift may not be mature enough