News for hackers. Stuff that matters.

A comment on Keeping Memory Contents Secret. Parent comment

Re:Keeping Memory Contents Secret by pjmlp on Monday November 25, 2019 @04:41AM (#21626672)
Sadly yes, while ARM and SPARC bounds checking get used to tame C and its derived languages, Intel decides to retire MPX.
[ Parent | on HN ]
Re:Keeping Memory Contents Secret by saagarjha on Monday November 25, 2019 @04:57AM (#21626731)
Apparently MPX had a number of issues in general that made it worse than tools like Address Sanitizer: https://arxiv.org/pdf/1702.00719.pdf
[ Parent | on HN ]
Re:Keeping Memory Contents Secret by pjmlp on Monday November 25, 2019 @05:48AM (#21626956)
I know, but then the path forward would be to fix it, instead of dropping it on the floor without any plan going forward.

After all, SPARC ADI is used in production, and ARM as well (partially with iOS, enforced in future Android devices).

[ Parent | on HN ]
Re:Keeping Memory Contents Secret by saagarjha on Tuesday November 26, 2019 @05:00AM (#21636915)
What feature does iOS have that that is similar to this?
[ Parent | on HN ]
Re:Keeping Memory Contents Secret by pjmlp on Wednesday November 27, 2019 @09:43AM (#21648198)
Pointer authentication and hardened runtime.
[ Parent | on HN ]
Re:Keeping Memory Contents Secret by saagarjha on Wednesday November 27, 2019 @11:08AM (#21649046)
Those don’t really catch memory safety issues in the general case; they’re more focused on exploit mitigation.
[ Parent | on HN ]