3 ms·

The key is on the console (not server side). Historically either they made some silly choices or there was a hardware bug or glitch that let you read out the ke

The key is on the console (not server side). Historically either they made some silly choices or there was a hardware bug or glitch that let you read out the key that the processor has to be able to access to decrypt the firmware. Search YouTube for fail0verflow and there are some great CCC talks very approachable and understandable about how it was done on other consoles historically. PS4: https://youtu.be/QMiubC6LdTA https://youtu.be/QMiubC6LdTA Wii U: https://youtu.be/oss_dwj-IkE https://youtu.be/oss_dwj-IkE

codetrotter 5y ago
What I don’t understand is why they don’t employ a second pair of keys, that the console only has the public key part of. Encrypt with one key pair, sign with another. And if the console had the public key part only of the signing key, it could first verify the signature with that public key before decrypting the payload with private key of the key pair used for encryption. People would still be able to decrypt the firmware by extracting the private key, and they could still find exploitable bugs in the firmware, but they would be unable to sign custom firmware, since the console would not hold the private key of the signing keypair. Has it been confirmed that the private keys that have been extracted would allow one to run custom firmware on the PS5? Or is Sony already doing something like what I am suggesting here, and thereby protecting against custom firmware for the PS5?