Talk:Seeds: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
= Further Help on finding the crypto ocurrences in N's twitter (and other ones aswell)=
= Some Clarifications for Keys by Sony (will be added later) =


It is necessary to do some investigation, and these things might help:
secure_com_lib_internal_key::FactoryInit_Password -> 2EA267093B4556ED9D3BE62E115D6D59


* unselfing every self possible and seek for hardcoded data inside the elf
secure_com_lib_internal_key::SC_BE_PayloadKey -> 6933CEE7A518E5B8CBE1FC14B261B765


* read the metadata of the self using readself(2) and encoded print_hash function
secure_com_lib_internal_key::SC_BE_PayloadKey -> A3ADB99A21E47ADFF3FD7FC3173981CA


**print_hash accepts two parameters (offset,length) where offset is where you want to localize the position and length is the lenght printed in bytes
secure_com_lib_internal_key::MAGIC -> 0xAD1A0000000000000000000000000000
 
* reverse engineering (whoever is capable of this and wants to give it a try is welcome to do so)
 
If i wasn't dumb to look for this, then certainly you, whomever you are, are not, and you're welcome to give it a shot at this :)
 
Good Luck
 
= Theory about EID1 and EID4 =
 
* EID4 shows the omac of the decrypted values in plain form when in encrypted state
 
example:
 
ENCRYPTED
<pre>
AA F3 F9 3F CB 2C 10 97 C1 24 6A C7 1B 72 79 0B
88 B1 00 0E 9B 0D 95 A3 D7 3E 3E 9C 6F 40 32 D0
04 33 3E 57 7E 1C ED 87 FA 92 56 09 28 48 34 31
</pre>
 
DECRYPTED
<pre>
02 0F 2A 40 2F 6B 0F 38 47 CB AC 2A B2 E1 5B D9
C1 BC 45 64 6D C5 E7 DB 51 3A 4C B7 FF 7B 4E F3
</pre>
 
the 3rd 16 byte value in the encrypted section is the hash in cmac-mode of the decrypted 32 bytes
 
* the same happens in EID1
 
assuming this, are we safe to say eid1 is ALREADY decrypted OR does it contain aditional crypto layers?
if it IS decrypted, what is inside it? they're exactly 640 bytes. that'd give room to 40 16 byte keys or 10 64 byte seeds.
 
= Other undocumented crypto stuff =
 
== sc_iso ==
 
k1: 3B050A7CA2961582228EE8029E4159D5
k2: C367A9AA6A166128B794883E61588B48
pub: 97A66090C2B61AC166162FBD85652EF3D3C040A81A9F7BD51006DD1D3F3E2E2B726F985014577D4B
 
== sb_iso ==
 
k1: 2B05F7C7AFD1B169D62586503AEA9798
k2: 74FF7E5D1D7B96943BEFDCFA81FC2007
k3: 30479D4B80E89E2B59E5C9145E1064A9
k4: 64E30D19A16941D677E32EEBE07F45D2
 
== sv_iso ==
 
k1: 17C0750CF94A32F15B761DEAD5213E86
 
== fdm ==
 
k1: BC3F7A48AF45EF283A0598103FE8793A
k2: DA48D52C75E54D7057A41EB5AE32166E

Revision as of 22:08, 26 May 2015

Some Clarifications for Keys by Sony (will be added later)

secure_com_lib_internal_key::FactoryInit_Password -> 2EA267093B4556ED9D3BE62E115D6D59

secure_com_lib_internal_key::SC_BE_PayloadKey -> 6933CEE7A518E5B8CBE1FC14B261B765

secure_com_lib_internal_key::SC_BE_PayloadKey -> A3ADB99A21E47ADFF3FD7FC3173981CA

secure_com_lib_internal_key::MAGIC -> 0xAD1A0000000000000000000000000000