249w ago - Update: It's now confirmed as a fake guys.
Today Spanish PS3 Developer DemonHades has announced news that they may have decrypted the Sony PS3 HDD. We will update the 'rumor' status of this when more questions are answered of course.
Several PS3 Devs including NDT are currently investigating whether the method can be repeated in other PS3 consoles, or just for one console only (possibly brute-forced?) as it's already known the key differs between each.
Below is a picture of a font on the PS3 decrypted, followed by some preliminary (roughly translated) details:
The key is 512bytes is a sha1-4096 (512 bytes per sector). The key is xoreada own... To be sure it was not a simple xor as speculation... text still appears ... /cell_mw_cfs and more text:
The method I can/should I even say it is very close to an update could change the key or decryption/encryption. The first is to investigate all of its content and then go looking at what interests us is that we have to go 40gbs decoding one by one and is not easy.
But since you said that all the published info that this method allows for and is something that decode the hdd, as advice... I will not make an actualizar. It's about read PS3 hdd content (512 bytes xored key has been decoded), by the moment this means that hard disk content could be read, but not all info about this have been revealed.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
It Looks like it was vreated in a Hex App. AES is hard to Dyencrypt, 512 is alot more than that Im used to, They could also be using the same concept as the yubico yubikey found at "http://www.yubico.com"
Well, although we all hope this is true, I do have a few issues with it so far...
For starters, SHA1 is a hashing mechanism , you can't use it to encrypt and decrypt data (not like AES, etc), its a one way hash.
Now, it may be possible that the SHA1 hash (which, is only 160 bytes) is the result of the SHA of some string (as in, the "password"), and the hash is used to decrypt the data, but, it was stated that the key was 512 bytes, not 160 bytes.
Furthermore, I doubt that the "password" would be stored anywhere on the hdd (not encrypted that is), as that would be insanely foolish to do.
Also, the "proof" that was posted so far (a font file), is not proof at all, I will dig up some files and reply with more info on them later.