Re:An iOS zero-click radio proximity exploit odyssey
by saagarjha on Wednesday December 02, 2020 @05:21AM
(#25275108)
Note that this code is shipping as a kernel extension, which uses Embedded C++, not standard C++. Notably, things like templates and exceptions are not available. It would be nice if they could work on this instead, but looking at the dyld and Security sources (which has no such limitations, as the run in userspace) I don't have much confidence.
Re:An iOS zero-click radio proximity exploit odyssey
by pjmlp on Wednesday December 02, 2020 @05:52AM
(#25275259)
They could still make use of bounds checking, like my own classes did back in the MS-DOS days, when C++ARM was pretty much the only thing available.
Naturally when one writes C in C++ it doesn't help.
Re:An iOS zero-click radio proximity exploit odyssey
by saagarjha on Wednesday December 02, 2020 @06:05AM
(#25275325)
I suspect that they'll adopt MTE first.
Re:An iOS zero-click radio proximity exploit odyssey
by pjmlp on Wednesday December 02, 2020 @07:08AM
(#25275631)
I agree, that was the path taken by Solaris SPARC and it is the only way to make it work, because even if a language level safety would be introduced today, not everyone would bother adopting it.
If they haven't kept up with the changes in their current language, what makes one think that they would "move on" to the alternatives, two of which aren't even alternatives?
Before they switch to Rust it would be much faster and more efficient to use smart pointers, std::array, std::vector and stop using memcpy.