An iOS zero-click radio proximity exploit odyssey

Re:An iOS zero-click radio proximity exploit odyssey by pjmlp on Wednesday December 02, 2020 @06:02AM (#25275312)

Microsoft is already kind of doing it, if you compile in debug mode, you get bounds checking in all STL types, and you can enable them in release builds as well.

But yeah, it only works if you use those types.

There are other divisions pushing for .NET and Rust systems code in Windows, but the political wars between WinDev and DevTools are quite well known, e.g. Longhorn (in .NET) vs WinRT (same thing just in COM).

[ Parent | on HN ]

Re:An iOS zero-click radio proximity exploit odyssey by Gibbon1 on Wednesday December 02, 2020 @02:57PM (#25280786)

Proper thing is bounds checking should be by default and you actually have to turn it off for hot path code. Because 99% of the code people write isn't memory or CPU bound. If a little used code path is sometimes throwing bounds exceptions you want that to get logged in production.

[ Parent | on HN ]

Re:An iOS zero-click radio proximity exploit odyssey by pjmlp on Wednesday December 02, 2020 @03:10PM (#25280932)

Check C.A.Hoare Turing award speech in 1981 regarding the use of bounds checking in the 60's and how customers of Algol compilers considered a legal offence to even turn them off.

[ Parent | on HN ]

Re:An iOS zero-click radio proximity exploit odyssey by lorenzhs on Wednesday December 02, 2020 @08:07AM (#25275966)

libstdc++ also has a debug mode with bounds checking etc, although you have to enable it by defining _GLIBCXX_DEBUG: https://gcc.gnu.org/onlinedocs/libstdc++/manual/debug_mode.h...

[ Parent | on HN ]

Re:An iOS zero-click radio proximity exploit odyssey by pjmlp on Wednesday December 02, 2020 @09:31AM (#25276627)

Thanks for the heads up.

[ Parent | on HN ]