News for hackers. Stuff that matters.
Re:A Look at iMessage in iOS 14 by pjmlp on Friday January 29, 2021 @02:14AM (#25954897)
Even if it turns out to be a bit slower, it is the pursuit of speed at the expense of bounds checking that has brought us here, although other ill fated OSes proved that it didn't had to be that way.
Re:A Look at iMessage in iOS 14 by astrange on Friday January 29, 2021 @03:24AM (#25955242)
Exploitations like this are much more complicated than lacking bounds checking; after all most web exploits start by defeating the supposedly memory safe JS interpreter.
Re:A Look at iMessage in iOS 14 by pjmlp on Friday January 29, 2021 @04:01AM (#25955441)
Because they trigger bugs in the underlying engine code written in C and C++.
Re:A Look at iMessage in iOS 14 by astrange on Friday January 29, 2021 @01:00PM (#25960266)
If your JIT interpreter is written in a safe language it can still have memory bugs because it’s generating and executing assembly directly.
Re:A Look at iMessage in iOS 14 by pjmlp on Friday January 29, 2021 @02:23PM (#25961230)
It might, just like the microcode, firmware and hardware design can have such bugs.

Safe languages don't magically make all code impossible to exploit, they just reduce the attack surface to logical errors, instead of having to deal with UB and memory corruption as well.

The same way that helmets and belts don't save people from dying all in all kinds of accidents, yet they surely help reducing the mortality numbers.

I enjoy languages with helmets and belts.

Re:A Look at iMessage in iOS 14 by wizzwizz4 on Friday January 29, 2021 @02:16PM (#25961139)
That sounds like a challenge.