ARM Pointer Authentication [2017]
1–10 of 16 posts
Re: ARM Pointer Authentication [2017]
#2Re: ARM Pointer Authentication [2017]
#3Re: ARM Pointer Authentication [2017]
#4Protection was partially hacked with: https://pacmanattack.com
[edit: this is also a 2017 article (I hadn't realized originally, cheers @dmytrish) so the gcc, etc support comments are presumably outdated]
Re: ARM Pointer Authentication [2017]
#5Protection was partially hacked with: https://pacmanattack.com
That is Apple silicon specific (at least for now?) as it isn’t a behaviour inherent to the ISA but rather it is yet another cache related side channel. It is of course entirely possible that other vendors will have the same info leak, but that particular paper seemed to be only interested in Apple hardware - I’m unsure how widely deployed PAC is in other vendor hardware so don’t know how feasible testing is. [edit: t…
Re: ARM Pointer Authentication [2017]
#6Re: ARM Pointer Authentication [2017]
#7Earlier quoted context omitted.
That is Apple silicon specific (at least for now?) as it isn’t a behaviour inherent to the ISA but rather it is yet another cache related side channel. It is of course entirely possible that other vendors will have the same info leak, but that particular paper seemed to be only interested in Apple hardware - I’m unsure how widely deployed PAC is in other vendor hardware so don’t know how feasible testing is. [edit: t…
If I recall that paper properly, they chose to do their work on the M1 because it was the only available chip with PAC at the time.
Re: ARM Pointer Authentication [2017]
#8Re: ARM Pointer Authentication [2017]
#9Does anyone know if that is still the case?