[arwynj55]

Originally Posted by tjhooker73 If we could do a constant dump of the PS3 Memory and processes while its starting up I think we could get a key or 2 :P

so worth it XD

[oPolo]

Hi @FaxiY

To explain it very simple, when you hear about public/private keys from someone, they are talking about asymmetric encryptions. (Although, some people are IMHO retards, and calls the secret key in symmetric encryption the private key... makes it confusing as hell)

Asymmetric encryption is where one key is used for encrypting and one is used for decrypting. The beauty of all this is that Sony can make one key rather public (the public key, which IIRC is stored in the ps3) and keep one key for themselves, the private key.

Every PS3 has the public key, so we can say the public key is relatively insecure, but only Sony has the corresponding private key for that public key. Thus, every firmware that is encrypted with the private key, can be verified by the playstation 3, as being from Sony as it can be decrypted (Sony in this sense "signs" the firmware) with the public key.
Even if we are in possession of the public key, we cannot encrypt (sign) the firmware as being from Sony, as we do not have the private key.

We cannot deduce the private key from the public key either, as the probably without a doubt most important characteristic of any asymmetric encryption, is that it is computationally infeasible, to deduce one key from the other

This is where Sony went wrong with their encryption implementation fail that was discovered in FW 3.55, and corrected in all firmware revisions to be released afterwards....
They made the mistake of, instead of using a random number in the ECDSA asymmetric encryption algorithm, they had basically made a method that said:

int getRandomNumber(){
return 4;
}

Or in layman's terms, instead of using a random number they always used the same number.
This removed the computationally infeasible aspect of the ECDSA algorithm, and allowed failoverflow to deduce the private key from the public key in the PS3, which has allowed us to sign any CFW and have the PS3 accept it, up till firmware 3.55.
After firmware 3.55, they fixed the ECDSA implementation **** up, and revoked a new keypair and made a new, which we are not able to deduce the private key from, should we obtain the public key.

Therefore, the private key is not stored in the PS3 Hope you understood it.

Ethos = Taking a computer security major ... Although, I don't really know any specifics about the ECDSA algorithm (and have never looked more than a few hours at the PS3's security), except that it is one of the promising algorithms for asymmetric cryptology in the future, instead of the current RSA algorithm that is widely accepted as THE asymmetric encryption algorithm right now. (I wrote this paragraph mainly to brag actually I don't give a damn if you decide to believe what I wrote or think it was all bull**** ._. Although it would hurt me ._.

[RafaSimpsons]

The problem about Sony is that it cares more than it should about security and money. The consequences are visible, you just have to look to the Xbox and Wii sales in relation to the PS3.

An example of Sony's ****ty behaviour is the Cobra dongle. They have the private keys, but did they appeared in front of their ugly faces? No, of course not. Sony has ****ed with them and it liked, so it gave them the keys.

[tjhooker73]

Originally Posted by RafaSimpsons The problem about Sony is that it cares more than it should about security and money. The consequences are visible, you just have to look to the Xbox and Wii sales in relation to the PS3. An example of Sony's ****ty behaviour is the Cobra dongle. They have the private keys, but did they appeared in front of their ugly faces? No, of course not. Sony has ****ed with them and it liked, so it gave them the keys.

The PS3 actually has more sales then the 360 now. So your statement is invalid.
http://www.digitaltrends.com/gaming/...consoles-sold/

[jarmster]

Do we have any idea what kind of random number it is? Whole number? number of possible decimal places? or are those specifics unknown?

[arwynj55]

Originally Posted by oPolo Hi @FaxiY To explain it very simple, when you hear about public/private keys from someone, they are talking about asymmetric encryptions. (Although, some people are IMHO retards, and calls the secret key in symmetric encryption the private key... makes it confusing as hell) Asymmetric encryption is where one key is used for encrypting and one is used for decrypting. The beauty of all this is that Sony can make one key rather public (the public key, which IIRC is stored in the ps3) and keep one key for themselves, the private key. Every PS3 has the public key, so we can say the public key is relatively insecure, but only Sony has the corresponding private key for that public key. Thus, every firmware that is encrypted with the private key, can be verified by the playstation 3, as being from Sony as it can be decrypted (Sony in this sense "signs" the firmware) with the public key. Even if we are in possession of the public key, we cannot encrypt (sign) the firmware as being from Sony, as we do not have the private key. We cannot deduce the private key from the public key either, as the probably without a doubt most important characteristic of any asymmetric encryption, is that it is computationally infeasible, to deduce one key from the other This is where Sony went wrong with their encryption implementation fail that was discovered in FW 3.55, and corrected in all firmware revisions to be released afterwards.... They made the mistake of, instead of using a random number in the ECDSA asymmetric encryption algorithm, they had basically made a method that said: int getRandomNumber(){ return 4; } Or in layman's terms, instead of using a random number they always used the same number. This removed the computationally infeasible aspect of the ECDSA algorithm, and allowed failoverflow to deduce the private key from the public key in the PS3, which has allowed us to sign any CFW and have the PS3 accept it, up till firmware 3.55. After firmware 3.55, they fixed the ECDSA implementation **** up, and revoked a new keypair and made a new, which we are not able to deduce the private key from, should we obtain the public key. Therefore, the private key is not stored in the PS3 Hope you understood it. Ethos = Taking a computer security major ... Although, I don't really know any specifics about the ECDSA algorithm (and have never looked more than a few hours at the PS3's security), except that it is one of the promising algorithms for asymmetric cryptology in the future, instead of the current RSA algorithm that is widely accepted as THE asymmetric encryption algorithm right now. (I wrote this paragraph mainly to brag actually I don't give a damn if you decide to believe what I wrote or think it was all bull**** ._. Although it would hurt me ._.

hope this wasnt pointed to me :P too long for me to read XD

[DEFAULTDNB]

Originally Posted by arwynj55 hope this wasnt pointed to me :P too long for me to read XD

Originally Posted by oPolo Hi @FaxiY

Nope

I think some bright-minded-individuals will figure out a bypass, or an exploit to do what we need without knowing any keys or anything..... eventually.

[arwynj55]

Originally Posted by DEFAULTDNB Nope I think some bright-minded-individuals will figure out a bypass, or an exploit to do what we need without knowing any keys or anything..... eventually.

lets just hope so my friend

[santimaster2000]

Wait, wait, wait, but, if we in fact get the lv0.2 keys, can't we just use a flasher ? I mean, wasn't this what was stopping flashers to work on 3K and 4K models, the fact we don't know this key ?

What I'm saying is:

1) Get a dump

2) Patch stuff with lv0.2 keys

3) Flash

4) Profit

PD: I'm not drunk but I'm hungry.

[carldenning]

if u wanna hack 3000 and 4000 models/lv 0.2 then ask the dev's who sold out , as their the w**k**s who knows