Editing Talk:BD Drive Reverse Engineering
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
= Getting keys the easier way = | = Getting keys the easier way = | ||
First you need to get the sv_iso_spu_module.self individuals seed that can be found in the metadata header: | First you need to get the sv_iso_spu_module.self individuals seed that can be found in the metadata header: | ||
<pre> | |||
3E C2 XX XX XX XX XX XX XX XX XX XX XX XX XX XX | |||
04 29 XX XX XX XX XX XX XX XX XX XX XX XX XX XX | |||
3D E0 XX XX XX XX XX XX XX XX XX XX XX XX XX XX | |||
1B A3 XX XX XX XX XX XX XX XX XX XX XX XX XX XX | |||
</pre> | |||
Using your console specific eid_root_key/iv (e.g. from metldr dump) and libeeid (insert the seed in keys.c) you can then decrypt EID4 directly by calling | Using your console specific eid_root_key/iv (e.g. from metldr dump) and libeeid (insert the seed in keys.c) you can then decrypt EID4 directly by calling | ||
< | <pre> | ||
u8 eid4[0x30] = {/* your EID4 */}; | |||
eid4_decrypt_buffer(eid4); | |||
</ | </pre> | ||
Now you got the two keys you need in eid4+0x00 and eid4+0x10 :) | Now you got the two keys you need in eid4+0x00 and eid4+0x10 :) | ||