Post: How signing works and how Sony gets the private key [ECDSA]
03-27-2013, 08:24 AM #1
(adsbygoogle = window.adsbygoogle || []).push({}); This is info from Crypto++'s wiki.

Private key generation:
    
AutoSeededRandomPool prng;
ECDSA<ECP, SHA1>::PrivateKey privateKey;

privateKey.Initialize( prng, ASN1::secp160r1() );
bool result = privateKey.Validate( prng, 3 );
if( !result ) { ... }


Public key generation [How to get it from the private key]:
    
privateKey.MakePublicKey( publicKey );

bool result = publicKey.Validate( prng, 3 );
if( !result ) { ... }


Once the public key has been derived, the public element can be retrieved as follows.
    
const ECP::Point& q = publicKey.GetPublicElement()

const Integer& qx = q.x;
const Integer& qy = q.y;


Now for the signing!

To generate a private key for signing using a Signer, perform the following.
    
AutoSeededRandomPool prng;
ECDSA<ECP, SHA1>::Signer signer;

signer.AccessKey().Initialize( prng, ASN1::secp160r1() );
bool result = signer.AccessKey().Validate( prng, 3 );
if( !result ) { ... }


We can also use a PrivateKey to initialize a signer:
    
ECDSA<ECP, SHA1>::PrivateKey privateKey
...
ECDSA<ECP, SHA1>::Signer signer(privateKey);

bool result = signer.AccessKey().Validate( prng, 3 );
if( !result ) { ... }
(adsbygoogle = window.adsbygoogle || []).push({});

The following 9 users say thank you to Dr. Mayham for this useful post:

631, AwesomeFaceHD, RTE Modz, Dacoco, xkoeckiiej, zPrimeModz, Zwiik

The following 6 users groaned at Dr. Mayham for this awful post:

Bad Luck Brian, jannu22, Killer1478, smashedya, Swifter, Wretch 32
03-29-2013, 03:26 PM #11
Originally posted by xxmcvapourxx View Post
*cough openssl ecdsa.h opps shit let that slip lol


A header file would do nothing to help though.
03-29-2013, 05:29 PM #12
Originally posted by Killer1478 View Post
A header file would do nothing to help though.


How do you know this? have you even looked into it or even understand what ECDSA mean's all it is a mathematics algor nothing more nothing less,infact if you read up ecies it use's the same key pair as ecdsa,and if you look at psn you would find out the authentication server generates random key's aka cipher encrypted handshake message ill give you a clue look for MD2RSA when you sign onto psn.if you want to know more join me on irc efnet #ps3dev! most of the dev's will agree with me on this !
03-29-2013, 05:59 PM #13
ryu2050
Treasure hunter
In short
No one can breach ECDSA, so therefore no jailbreak on new firmware greater than 3.56
Live with the fact!!!
03-29-2013, 11:03 PM #14
that's nothing new Smile
03-30-2013, 04:56 PM #15
Originally posted by xxmcvapourxx View Post
How do you know this? have you even looked into it or even understand what ECDSA mean's all it is a mathematics algor nothing more nothing less,infact if you read up ecies it use's the same key pair as ecdsa,and if you look at psn you would find out the authentication server generates random key's aka cipher encrypted handshake message ill give you a clue look for MD2RSA when you sign onto psn.if you want to know more join me on irc efnet #ps3dev! most of the dev's will agree with me on this !



It's a header, if you really think a bunch of #include blahblahblah.h is gonna help anyone with cracking sony's private key you'd be wrong.
03-30-2013, 05:14 PM #16
riggstq
[move]Haters Gonna Hate[/move]
Originally posted by ryu2050 View Post
In short
No one can breach ECDSA, so therefore no jailbreak on new firmware greater than 3.56
Live with the fact!!!


that isnt a fact people can isntall cfw over 3.60 they need to genreate there per console data and then mod the pup accordingly one thing that wont ever be possible again is a release of a cfw that installs on ALL ps3s above 3.60 as the data is constantly changing from console to console correct me if im wrong but i remember reading this from a reliable source
03-30-2013, 05:33 PM #17
This thread is going nowhere. May I request that a mod closes this please?
03-31-2013, 01:30 AM #18
ryu2050
Treasure hunter
Originally posted by riggstq View Post
that isnt a fact people can isntall cfw over 3.60 they need to genreate there per console data and then mod the pup accordingly one thing that wont ever be possible again is a release of a cfw that installs on ALL ps3s above 3.60 as the data is constantly changing from console to console correct me if im wrong but i remember reading this from a reliable source


You are wrong bro hackers need to crack the ECDSA sig of the firmware so that the ps3 thinks the .pup update came from Sony.Otherwise we can have as many and future cfw but we will not be able to install them.this only applies for firmware greater than 3.56.
Since hacking of ecdsa is near impossible so installing a cfw over ofw greater than 3.56 is out of the question!!!
04-01-2013, 02:45 AM #19
Originally posted by ryu2050 View Post
In short
No one can breach ECDSA, so therefore no jailbreak on new firmware greater than 3.56
Live with the fact!!!

The best thing we can hope for is a USB downgrader, but I'm not sure if that is possible, either.

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo