How signing works and how Sony gets the private key [ECDSA]

03-27-2013, 08:24 AM #1

Dr. Mayham

Banned

470

Posts

8,293

Reputation

0

Credits

Banned

Oct 2011

NextGenUpdate

(adsbygoogle = window.adsbygoogle || []).push({}); This is info from Crypto++'s wiki.

Private key generation:

    

AutoSeededRandomPool prng;

ECDSA<ECP, SHA1>:rivateKey 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:oint& 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>:rivateKey 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-27-2013, 10:40 AM #2

ELITE xxmcvapourxx

Guest

n/a

Posts

n/a

Reputation

n/a

Credits

Member

Once upon a time...

NextGenUpdate

Now think after all this posting,Please say to me how you going to get this? its not in ps3 think closer where else it would be maybe the authentication server from sony or edgekey? which one 0_o

03-27-2013, 12:19 PM #3

QuantumDev

Can’t trickshot me!

403

Posts

938

Reputation

63

Credits

Member

Jan 2013

NextGenUpdate

I have just one question. Can't you sign homebrew just like on the PSP, so you can run FTP Server and such on the PS3, without CFW?

03-27-2013, 12:44 PM #4

xkoeckiiej

At least I can fight

2,344

Posts

7,320

Reputation

761

Credits

Member

Feb 2011

NextGenUpdate

Originally posted by xQuantumModz

I have just one question. Can't you sign homebrew just like on the PSP, so you can run FTP Server and such on the PS3, without CFW?

no since you don't got the private key.

03-27-2013, 08:46 PM #5

iOdysseus

Bounty hunter

160

Posts

1,583

Reputation

0

Credits

Member

May 2012

NextGenUpdate

LOL. You think your a hacker for this useless information? Not trying to bash on you. This information is 100% easy to get. Hell, you could download the ECDSA library and apply it to your own program...

03-27-2013, 09:45 PM #6

Killer1478

Winning.

230

Posts

2,216

Reputation

0

Credits

Premium

May 2010

NextGenUpdate

Originally posted by 00x0

This is info from Crypto++'s wiki.

If its copy pasta from a wiki, why even post it. I highly doubt anyone who would even attempt to break ECDSA would look here for publicly available information

03-28-2013, 06:51 PM #7

Bichote

Former Staff

5,912

Posts

94,393

Reputation

12

Credits

NextGenUpdate Elite

Nov 2009

NextGenUpdate

Originally posted by 00x0

This is info from Crypto++'s wiki.

Private key generation:

    

AutoSeededRandomPool prng;

ECDSA<ECP, SHA1>:rivateKey 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:oint& 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>:rivateKey privateKey

...

ECDSA<ECP, SHA1>::Signer signer(privateKey);



bool result = signer.AccessKey().Validate( prng, 3 );

if( !result ) { ... }

You must login or register to view this content.
lol

03-28-2013, 07:31 PM #8

ELITE xxmcvapourxx

Guest

n/a

Posts

n/a

Reputation

n/a

Credits

Member

Once upon a time...

NextGenUpdate

Originally posted by Killer1478

If its copy pasta from a wiki, why even post it. I highly doubt anyone who would even attempt to break ECDSA would look here for publicly available information

*cough openssl ecdsa.h opps shit let that slip lol

03-28-2013, 10:10 PM #9

CodModder86

Banned

281

Posts

1,047

Reputation

0

Credits

Banned

Nov 2012

NextGenUpdate

Originally posted by 00x0

This is info from Crypto++'s wiki.

Private key generation:

    

AutoSeededRandomPool prng;

ECDSA<ECP, SHA1>:rivateKey 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:oint& 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>:rivateKey privateKey

...

ECDSA<ECP, SHA1>::Signer signer(privateKey);



bool result = signer.AccessKey().Validate( prng, 3 );

if( !result ) { ... }

i have posted bad posts in my time Happy

but this is a joke lol ya hardly copied and pasted ?
because THATS BULLSHIT information...
I get this enformation in 10secs with out your help Smile

its a pity its not easy when you want to get a jailbreak out of it Happy

and no im not hateing

03-29-2013, 09:56 AM #10

ShattiUnique

Guest

n/a

Posts

n/a

Reputation

n/a

Credits

Member

Once upon a time...

NextGenUpdate

Originally posted by 00x0

This is info from Crypto++'s wiki.

Private key generation:

    

AutoSeededRandomPool prng;

ECDSA<ECP, SHA1>:rivateKey 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:oint& 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>:rivateKey privateKey

...

ECDSA<ECP, SHA1>::Signer signer(privateKey);



bool result = signer.AccessKey().Validate( prng, 3 );

if( !result ) { ... }

thanks man Winky Winky