[Persian McLovin]

Originally Posted by baargle 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.

I thought your analogy was pretty good!

[varaques]

Originally Posted by carldenning u dont need to tell me . if u read the thread, u would see that im one off the people that telling people that to have a higher cfw that install on 3.56+ ofw we need private keys. and to get them u would need to rob sony office cos the private keys are not in the ps3 .

after 3.55 cfw Sony put a randomizer to make it harder to find the private keys

[baargle]

Originally Posted by varaques after 3.55 cfw Sony put a randomizer to make it impossible to find the private keys

He knows that, he was talking rhetorically. Just to be clear and avoid a further question from the noobs, I have fixed your post

[Noxxx]

Originally Posted by DEFAULTDNB Dont give up, there are people working on it Even if it requires a modified flasher, it will be done eventually.

Im starting to find nearly to impossible , just facing the facts a ps3 with OFW 4.25 will never be broken , maybe time to move on to another option too bad cause i love my ps3 !!

[chosela]

Originally Posted by baargle 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.

The key is in the PS3. Otherwise it cannot know whether firmware updates are legit or not. Doesn't matter if they use both key to generate a public-private key combination, the console would still need those two keys to verify the final key validity. You would have to update the console while connected to the internet to get a remote server validation to update a PS3 that doesn't know the key, server which would have the key on it, otherwise IT CANNOT VALIDATE THE KEY. A computer cannot test something against an answer it doesn't have, now that's impossible. The key is in the software, well hidden, but it's in there.

[hintgiver]

Originally Posted by chosela The key is in the PS3. Otherwise it cannot know whether firmware updates are legit or not. Doesn't matter if they use both key to generate a public-private key combination, the console would still need those two keys to verify the final key validity. You would have to update the console while connected to the internet to get a remote server validation to update a PS3 that doesn't know the key, server which would have the key on it, otherwise IT CANNOT VALIDATE THE KEY. A computer cannot test something against an answer it doesn't have, now that's impossible. The key is in the software, well hidden, but it's in there.

That is wrong, only the public key is used to test for integrity. The private key is only known to sony.

[zxz0O0]

spp_verifier 4.25 (probably 4.20 - 4.31):

Erk: D2961BBFFEDAEE269B061454D6ACF262CD71BC6F5320180F0A04A07583CCF7C5
Riv: 6D308B59BC9054B12C833359D31BAE77
Pub: 0CDD0D1541A6B0DFD12E951578536CA60C93853B88FCE17592DC8D134B08A94AF8BB08667E2D70A5
Curve: 07

If you want to use with scetool you have to use manual keyset (scetool is confused because both keysets 3.55 and 4.25 have revision 0)
************* [ - Post Merged - ] *************
rvklist 4.25 (probably 4.20 - 4.31):

Erk: 695984b7ee2ec2f77fcc3120150dce7e4480d84480ddd8c5940aeb6f79e63d17
Riv: a8ba3e4e63b2bb06fc0ce57e3bb8fc46
Pub: 7f1950c6e497e922400586ee338b41e01c906c5a6dfd75feb5249cfa4bec534f5ca679670a452b2a
Curve: 12

scetool format:

[rvk]
type=RVK
revision=00
version=00000002
erk=695984b7ee2ec2f77fcc3120150dce7e4480d84480ddd8c5940aeb6f79e63d17
riv=a8ba3e4e63b2bb06fc0ce57e3bb8fc46
pub=7f1950c6e497e922400586ee338b41e01c906c5a6dfd75feb5249cfa4bec534f5ca679670a452b2a
priv=
ctype=12

[Abkarino]

Originally Posted by zxz0O0 spp_verifier 4.25 (probably 4.20 - 4.31): Erk: D2961BBFFEDAEE269B061454D6ACF262CD71BC6F5320180F0A04A07583CCF7C5 Riv: 6D308B59BC9054B12C833359D31BAE77 Pub: 0CDD0D1541A6B0DFD12E951578536CA60C93853B88FCE17592DC8D134B08A94AF8BB08667E2D70A5 Curve: 07 If you want to use with scetool you have to use manual keyset (scetool is confused because both keysets 3.55 and 4.25 have revision 0) ************* [ - Post Merged - ] ************* rvklist 4.25 (probably 4.20 - 4.31): Erk: 695984b7ee2ec2f77fcc3120150dce7e4480d84480ddd8c5940aeb6f79e63d17 Riv: a8ba3e4e63b2bb06fc0ce57e3bb8fc46 Pub: 7f1950c6e497e922400586ee338b41e01c906c5a6dfd75feb5249cfa4bec534f5ca679670a452b2a Curve: 12 scetool format: [rvk] type=RVK revision=00 version=00000002 erk=695984b7ee2ec2f77fcc3120150dce7e4480d84480ddd8c5940aeb6f79e63d17 riv=a8ba3e4e63b2bb06fc0ce57e3bb8fc46 pub=7f1950c6e497e922400586ee338b41e01c906c5a6dfd75feb5249cfa4bec534f5ca679670a452b2a priv= ctype=12

Revokation List key are confirmed by me with 4.31 prog.srvk using scetool:

C:\Users\MHassan\Desktop\SCETools>scetool -i C:\Users\MHassan\Desktop\SCETools\p
rog.srvk
scetool 0.2.9 <public build> (C) 2011-2012 by naehrwert
NP local license handling (C) 2012 by flatz
[*] SCE Header:
 Magic           0x53434500 [OK]
 Version         0x00000002
 Key Revision    0x0000
 Header Type     [RVK]
 Metadata Offset 0x00000000
 Header Length   0x0000000000000200
 Data Length     0x00000000000000E0[*] Metadata Info:
 Key 05 51 4A D4 82 CD 77 0C C0 58 C1 53 3C B0 92 1B
 IV  B2 4E ED 49 39 2A 0D CB 03 58 15 9A F1 67 DD BD[*] Metadata Header:
 Signature Input Length 0x00000000000001C0
 unknown_0              0x00000001
 Section Count          0x00000002
 Key Count              0x0000000E
 Optional Header Size   0x00000000
 unknown_1              0x00000000
 unknown_2              0x00000000[*] Metadata Section Headers:
 Idx Offset   Size     Type Index Hashed SHA1 Encrypted Key IV Compressed
 000 00000200 00000020 01   01    [YES]  00   [NO ]     --  -- [NO ]
 001 00000220 000000C0 02   02    [YES]  06   [YES]     0C  0D [NO ][*] SCE File Keys:
 00: 80 B6 91 44 54 B7 D1 C1 8D 1A ED 39 81 7E E5 2F
 01: 84 21 9F 5E 00 00 00 00 00 00 00 00 00 00 00 00
 02: D0 BC 27 84 22 30 34 C8 21 DA 58 B6 F0 F7 4A E0
 03: C9 FC BC 30 9C A2 15 06 D5 BA 02 F6 FF CC 13 2A
 04: 63 BB 9C EF F8 D7 26 45 68 77 94 4C 66 9E A2 1B
 05: 87 09 C6 27 3C B7 79 2D 62 6E 14 90 66 F5 BD 86
 06: 4B B8 B8 38 51 20 BD 76 9F BA 83 66 04 75 EC 47
 07: 6C 84 1D D2 00 00 00 00 00 00 00 00 00 00 00 00
 08: D0 BC 27 84 22 30 34 C8 21 DA 58 B6 F0 F7 4A E0
 09: C9 FC BC 30 9C A2 15 06 D5 BA 02 F6 FF CC 13 2A
 0A: 63 BB 9C EF F8 D7 26 45 68 77 94 4C 66 9E A2 1B
 0B: 87 09 C6 27 3C B7 79 2D 62 6E 14 90 66 F5 BD 86
 0C: 5B D0 37 88 54 91 80 4C C1 F3 1F 70 AA 9D 0A B5
 0D: 17 CA FB 25 69 19 85 85 D1 3A E4 37 00 00 00 00[*] Revoke List Header:
 type_0      0x00000004
 type_1      0x00000001
 Version     04.31
 Entry Count 0x00000006[*] Program Revoke List Entries:
 Type                Check    Version Auth-ID/unk_3    Mask
 lv2                 ==       04.31   0000000000000002 FFFFFFFFFFFFFFFF
 Application         ==       04.31   vsh              FFFFFFFFFFFFFFFF
 Application         ==       04.31   10700005FE000001 FFFFFFFFFFFFFFFF
 Application         ==       04.31   sys_init_osd     FFFFFFFFFFFFFFFF
 Application         ==       04.31   sys_audio        FFFFFFFFFFFFFFFF
 Application         <=       01.00   1070000400000001 FFFFFFFFFFFFFFFF

Also here it it SPP keys in scetool format tested and working (4.31) also confirmed by me:

[spp]
type=SPP
revision=0000
version=00000002
erk=D2961BBFFEDAEE269B061454D6ACF262CD71BC6F5320180F0A04A07583CCF7C5
riv=6D308B59BC9054B12C833359D31BAE77
pub=0CDD0D1541A6B0DFD12E951578536CA60C93853B88FCE17592DC8D134B08A94AF8BB08667E2D70A5
priv=
ctype=07

Thanks for sharing.

[zxz0O0]

spu_pkg_rvk_verifier 4.25 (untested)

Erk: f8f99006f1c007d5d0b1909e9566e0e70b569399fc3394a811809fdb5cae92cd
Riv: 59d28db4addfb40b7d768bc9667c67b1
Pub: 5432bddd1f97418147aff016eaa6100834f2caa8c498b88965689ee44df349b066cd43cbf4f2c5d0
Curve: 17

[Abkarino]

Originally Posted by zxz0O0 spu_pkg_rvk_verifier 4.25 (untested) Erk: f8f99006f1c007d5d0b1909e9566e0e70b569399fc3394a811809fdb5cae92cd Riv: 59d28db4addfb40b7d768bc9667c67b1 Pub: 5432bddd1f97418147aff016eaa6100834f2caa8c498b88965689ee44df349b066cd43cbf4f2c5d0 Curve: 17

Sorry what do you mean by spu_pkg_rvk_verifier 4.25 this self use the same isoldr keys released before or this is another key for decrypting some thing else?