Seems very similar to Zenbleed in terms of using certain register optimisation and speculative execution to get crippling security exploits. Thus far I haven’t read too much into the detail of the attack but This article on Zenbleed, written by the attack’s author, describes how the attack in detail and how he came to find it using fuzzing techniques - in this case two sets of instructions that should have had the same result, but they didn’t.
The write-up for this one is presumably this one.
Here is a good write-up of Zenbleed for the Ryzen 2 and up vulnerability. It uses similar register optimisation and speculative execution to get the same effect.
deleted by creator
Great answer, it is similar to the cost parameter for bcrypt/scrypt and iterations for PBKDF2.
If you have an oximetry of 30%, you either have a potential zombie outbreak on your hands, or; your sensor is fucked and you need to adjust it.
Fixed that for you 👍
P.S. Thanks, that was a great read.
Ahh, the good old days.
Mostly I just wanted to make sure people who dislike updating, ‘because it might break stuff’ - are warned before hosting a lemmy instance. Do it on snapshot-able or reliable hardware if you are going to have people join.