John McKown wrote: >This is interesting. Reminds me a bit of IBM's newest "Pervasive Encryption".
>https://www.theregister.co.uk/2017/06/20/amd_epyc_launch/ Interesting. So to grab a CPU is needing this condition - available and correct Private Key. "The key is generated during power-up by the BIOS, and should never leave the controller." What if there is a flaky memory or something? Say you generate the key and store it somewhere, but a bit is written as 1 instead of 0 or vice-versa. What do you do then? What checksum and fixing are there to fix it on the fly? Will that new trick stop that Meltdown/Spectre vulnerability? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
