[helmet]

Absolute bullcrap. Private\Public key encryption works where the private key is used to SIGN\ENCRYPT content. The public key is used to VERIFY\DECRYPT the content. The private key cannot be calculated from the public key. This is the beauty of Private\Public key encryption. It is one of the great developments of the past 20 years or so with virtually no implementations of it even using very simple key lengths - none broken by anything except commercial efforts, even then we're talking very short key lengths . The one's used in the PS3 is a magnitude times more difficult to break by brute force (the ONLY way to break it). It would take millions of years to retrieve the private keys that Sony uses with millions of computers all working together that is. The private key is NOT in the console and might not even be known by anyone in the world - even at Sony HQ. As if Sony had sense it would be possible to isolate the key on a computer system so only the software that signs it knows the key. Imagine throwing a dice in the dark and you have a number, you can't see it but an infra-red camera could. That dice number could then be used to sign all stuff that needs to be signed\encrypted. ...Terrible analogy but it explains the point.

That's not completly true, brute force the private key will not take millions of years ! Thats far from reality nowadays. Today brute force is done mostly on GPU side and its so fast that in fact no password that we use on our computer's is secure. As an example a ordinary AMD Radeon 5770 will brute force a 7 character alphanumeric + special character password in 7 hours while the CPU would need 75 days, now think about the newest GPU's or GPU's running in parallel or hardware that is only made for such operations and you are on milliseconds to get the password. 512bit or 1024bit RSA keys are counting as insecure nowadays maybe 2048bit allready too and the private key people are searching on this forum is only 160bit strong and public keys and curves are known. Super Computer power from 1999 are nowadays in our laptops.

[arwynj55]

Originally Posted by baargle If you add typing then pressing the post button, I timed it at 36.51 seconds. I called it 37 seconds cos I didn't like his post. ************* [ - Post Merged - ] ************* Private keys are strangely enough, private. In the sense that they aren't stored in anyway on the target platform. Stop thinking, it's bad for you.

I know the private keys arent in the ps3 :P mebey anonymous has them?

[aldostools]

Originally Posted by Abkarino Yea i had confirmed this keys and also updated the ps3devwiki page with the confirmed keys also

I see that in the wiki, the keys for rvklist and spp_verifier 4.00-4.11 were posted (but these key are wrong). They don't use the keys for rvk/spp 4.20-4.31.

The code below are the public keys/ctype/revision/self_type for some still missing appldr keys 3.65-4.00. The erk/riv values posted below are *ENCRYPTED* and cannot be used in the current state. I hope that this help at least to complete some fields in the wiki (upon verification)

Note: the revisions still need confirmation.

Click here to see full text

[appldr] type=SELF revision=0012 version=0003006000000000 self_type=APP //erk=34AAD9894BCFE96039E5547CA1A0C1B8674597493C476497BAA22BB841729376 //riv=4B51DD0A43A096CD9C32371747886092 pub=3C266FF46D1F526405CCCDD67EE9C7D5693B4A072C06988CAD22ADDB64439A32E2337722F51FC15B priv= ctype=3D [appldr] type=SELF revision=0015 version=0003006500000000 self_type=APP //erk=8D4AC5BA076323FAB1EB75A0BD115AC1A6066BD4E27706B2E57AD98AE56074FC //riv=F67AC48C015F894CF45319A8C05F4B6B pub=A6283C12B04C37DDC6EBBF4B31E5F1B1B2602DC83EBA6362C9C1189BF25A3EF1BB3766625A4E9694 priv= ctype=3A [appldr] type=SELF revision=0018 version=0003007000000000 self_type=APP //erk=D3170FB8B68FFD0C6B2C4E5B6BE552676B3A64CE8FA29677CCE772923B0DFAAD //riv=A78AC29C293B37AD05A69EB1AA505DF4 pub=64A04126D77BF6B4D686F6E8F87DD150A5B014BA922D2B694FFF4453E11239A6E0B58F1703C51494 priv= ctype=11 [appldr] type=SELF revision=001B version=0004000000000000 self_type=APP //erk=C776DABBC528A4387F98A14C3302D7B67C0A2D3274BAEDAEA336B4F46A16B3CB //riv=D0405F7310A5FD134C24190E92366C00 pub=4AB6FB1F6F0C3D9219923C1AC683137AB05DF667833CC6A5E8F590E4E28FE2EB180C7D5861117CFB priv= ctype=12 [appldr] type=SELF revision=0011 version=0003006000000000 self_type=NPDRM //erk=7F5084FB1E0734F275DCF57A3127FCC4E8D05FE2F1532D786175728D8BF4434A //riv=2126DF73EE8ACC47D512F2B8BE6D61EA pub=EA2F8826D1ECA47B029B41C833615006FAF535AAD30594319EA4F767925EBAE3A3EEE32E6D29580C priv= ctype=3A [appldr] type=SELF revision=0014 version=0003006500000000 self_type=NPDRM //erk=0A7036226313F356955A840CA5CB875C4BC9E88D4F9F36A3C6520D10EAEE2358 //riv=ED32ADBEFB43EC6A767C8E773D4F75C6 pub=497296C62F2C489F9F0E7628887AD54715EFD1227B053C6AA4501D43FF6FB536B78315C08D786569 priv= ctype=3B [appldr] type=SELF revision=0017 version=0003007000000000 self_type=NPDRM //erk=CE39FBDA7F1B31BBC353FDC30E8AEA50CA627FF6CFEA2B9C12EC9DD4DFD4A2C4 //riv=CB7CDB0EFB33E023D3343D0EF85DF82D pub=ABD149AB27BEE0DEC0E34BB8A8CA225E3FCF504E2DDE6A55BBD39A06CFB068CFC3CF5DF8B117EB5A priv= ctype=15 [appldr] type=SELF revision=001A version=0004000000000000 self_type=NPDRM //erk=7BADC9FFA0B4A6DE96EE50B145A68EE3FD28E454E2971467E26F250A78372231 //riv=E652A368E5EE3A440497D8DFEDD41B40 pub=4F30DF9F3A9D6B3AF92510F81F7961DD404F5E09BFF4D989969727509E39B94A750D12A063189848 priv= ctype=17

I find interesting that these keys are available in appldr 4.00 (and below), but they are not present in the appldr 4.20-4.31.

[Abkarino]

Originally Posted by aldostools I see that in the wiki, the keys for rvklist and spp_verifier 4.00-4.11 were posted (but these key are wrong). They don't use the keys for rvk/spp 4.20-4.31. The code below are the public keys/ctype/revision/self_type for some still missing appldr keys 3.65-4.00. The erk/riv values posted below are *ENCRYPTED* and cannot be used in the current state. I hope that this help at least to complete some fields in the wiki (upon verification) Note: the revisions still need confirmation. Click here to see full text I find interesting that these keys are available in appldr 4.00 (and below), but they are not present in the appldr 4.20-4.31.

It maybe not exist because may be Sony had changed the encryption algorithm from 4.xx to 4.2x.

[raulbz777]

bkpps3 cech-3006a.part1.rar

bkpps3 cech-3006a.part2.rarwith this dump i managed to brick and unbrick my ps3 cech 3006a with 4.25 ofw and e3 flasher with samsung update

[godking666]

i still say get xmb going on the pc emu. and instead of just the hdd0 folder get every folder. clone the ps3. then once the xmb functions install ofw 4.31 and run hulo or something that needs to verify and see what shows in the elf dialogue box. or try n sniff the key exchange via a pc instead. or even on a ps3 running linux use a ps3 emu in linux so the emu has full access to the ps3 and whatnot and the emu runs better. either way doing it on an os would make it easier to atleast attempt to get a peek into the process no?