AMD: Microcode Signature Verification Vulnerability
1–10 of 107 posts
Re: AMD: Microcode Signature Verification Vulnerability
#2What a load of shit! Confidence is earned, it does not grow back like a weed you stepped on!
Re: AMD: Microcode Signature Verification Vulnerability
#3Do we know what this "insecure hash function" is/was?
Re: AMD: Microcode Signature Verification Vulnerability
#4Re: AMD: Microcode Signature Verification Vulnerability
#5> we will not be sharing full details at this time in order to give users time to re-establish trust on their confidential-compute workloads. What a load of shit! Confidence is earned, it does not grow back like a weed you stepped on!
Re: AMD: Microcode Signature Verification Vulnerability
#6> CPU uses an insecure hash function in the signature validation Do we know what this "insecure hash function" is/was?
Re: AMD: Microcode Signature Verification Vulnerability
#7> we will not be sharing full details at this time in order to give users time to re-establish trust on their confidential-compute workloads. What a load of shit! Confidence is earned, it does not grow back like a weed you stepped on!
Re: AMD: Microcode Signature Verification Vulnerability
#8I would be tickled pink if the 4 was in reference to https://xkcd.com/221/
Re: AMD: Microcode Signature Verification Vulnerability
#9> A test payload for Milan and Genoa CPUs that makes the RDRAND instruction return 4 I would be tickled pink if the 4 was in reference to https://xkcd.com/221/
Re: AMD: Microcode Signature Verification Vulnerability
#10"A test payload for Milan and Genoa CPUs that makes the RDRAND instruction return 4"... Turns out kernel RNG belt-and-suspenders was justified?