Post: I'd like to get some input/help about PS3 keys
03-16-2011, 07:06 PM #1
(adsbygoogle = window.adsbygoogle || []).push({}); Ok, let me start out by saying that I am new to the PS3 scene, and I will admit that I am not good at it (I have a problem knowing where to start...), but I am very good at math.

I guess my question is really, how do you find the private key? I know it can be calculated by using fail0verflow's calculations, it's been done on previous firmwares. Or is it something that has to be found, dumped, decrypted, etc.?

I'm asking these questions, because there have been a lot of people saying that they have 3.56 priv keys, knows someone with them, what ever the case may be, I was hoping to get my math on and start cracking down some numbers!

I've read many tutorials, including a couple very nice ones on this site, and have the rest of the keys, but I can't seem to understand how to calculate the keys because they are Hex codes. Is there something that needs to be done first to the hex code (re-coded, stripped down, use only certain values) before it can be penciled out? I'd really like to give this a shot, though I'll probably get nothing out of my work, but it's the fun of the chase I guess...

As a side note, while the tutorials were very good, and helped me out, I don't think there was enough, not "noob friendly", but not so developmentally in-depth?

Please don't flame, tell me I'll never get it (I completely agree), or just be plain stupid in this thread, I'm trying to commit myself to helping this cause, because I never wanted 3.56, my buddy was "doing me a favor" when he was over, and for those who have remained on 3.56 as I have, I'd like to give them the second chance (or just me/trusted acquaintances... Leaking = Leeching n00bs).

If I make some progress, I'm glad to share it with this community, but if somehow I manage to become God, the finalized (or possible) key is going to the Devs on this site only. I guess from there, we'll see who gets it. I don't want to get caught up in this $ony lawsuit and sue happy crap though. I'll take my risks...
(adsbygoogle = window.adsbygoogle || []).push({});
03-16-2011, 08:17 PM #2
<Jimbo>
</Jimbo>
I'm pretty sure the way the Private key was found last time was due to an error Sony made... Just calculating the Priv using the return of the public being the same on each, thus not taking away the lenghty process! My guess would be that if you tryed to use the same method for 3.56 or 3.60 it's gonna take like thousand's of years :O The possibilitys are now almost infinite! :p
03-16-2011, 08:35 PM #3
Originally posted by 123tonka View Post
I'm pretty sure the way the Private key was found last time was due to an error Sony made... Just calculating the Priv using the return of the public being the same on each, thus not taking away the lenghty process! My guess would be that if you tryed to use the same method for 3.56 or 3.60 it's gonna take like thousand's of years :O The possibilitys are now almost infinite! :p


Ah, well that's a disappointment...

So, in other words, the formulas for the calculations would be different for 3.56+ than what fail0verflow released a while back? I know things have changed, and security tighter, but I thought it could be a lucky shot in the dark.

I can see how the same method wouldn't work, and one reason is because if it DID work for 3.56+, someone would have made a program to just punch in all the keys and get a private key in return, right?

Okay, so now that my mathematical dreams are crushed (I think that was the only way I could help..), can anyone set me on my feet and head me in the right direction on how to crack/find/dump/buttsecks the private keys? I'm very adaptive, and I learn rather quickly, and I can actually use my head and think "What next. Let's give this a try...".

As I said, if it's going to involve heavy math, bring it on; It'll be like a morning brain-teaser to me! (Maybe I'm exaggerating a bit...) :evil:
03-16-2011, 09:48 PM #4
Norman
NORMAN
Originally posted by x420x View Post
Ah, well that's a disappointment...

So, in other words, the formulas for the calculations would be different for 3.56+ than what fail0verflow released a while back? I know things have changed, and security tighter, but I thought it could be a lucky shot in the dark.

I can see how the same method wouldn't work, and one reason is because if it DID work for 3.56+, someone would have made a program to just punch in all the keys and get a private key in return, right?

Okay, so now that my mathematical dreams are crushed (I think that was the only way I could help..), can anyone set me on my feet and head me in the right direction on how to crack/find/dump/buttsecks the private keys? I'm very adaptive, and I learn rather quickly, and I can actually use my head and think "What next. Let's give this a try...".

As I said, if it's going to involve heavy math, bring it on; It'll be like a morning brain-teaser to me! (Maybe I'm exaggerating a bit...) :evil:


All that changed is the ecdsa code. We got the private keys by calculating them with the ecdsa code. There is no way to dump or read or ever get private keys realistically. The ecdsa number was four. If you want to learn more about this stuff pm me, we'll chat.
03-17-2011, 02:16 AM #5
Originally posted by norman View Post
All that changed is the ecdsa code. We got the private keys by calculating them with the ecdsa code. There is no way to dump or read or ever get private keys realistically. The ecdsa number was four. If you want to learn more about this stuff pm me, we'll chat.


Will do, I'm very interested in this. And whether the priv keys for 3.56 are out or not (kept secret/not released), I'd like to find them myself, as something to do, and somewhere to start myself in this scene.

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo