Editing 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: | ||
=Information about EID4= | =Information about EID4= | ||
* EID4 contains 2 128bit keys which are necessary to establish a secure communication channel to BD drive for sending vendor specific security commands. | * EID4 contains 2 128bit keys which are necessary to establish a secure communication channel to BD drive for sending vendor specific security commands. | ||
* EID4 is encrypted with AES-CBC- | * EID4 is encrypted with AES-CBC-128 algorithm. | ||
* EID4 is of size 0x30 bytes: 0x0-0xf bytes = 1st key, 0x10-0x1f - 2nd key, 0x20-0x2f - CMAC-OMAC1 of EID4 | * EID4 is of size 0x30 bytes: 0x0-0xf bytes = 1st key, 0x10-0x1f - 2nd key, 0x20-0x2f - CMAC-OMAC1 of EID4 | ||
* The first key is used for encrypting data sent from host to BD drive. | * The first key is used for encrypting data sent from host to BD drive. | ||
Line 14: | Line 10: | ||
* I modified sv_iso_spu_module.self to dump EID4 IV and key. | * I modified sv_iso_spu_module.self to dump EID4 IV and key. | ||
* I used | * I used spuisofs kernel module and the below SPU program to dump EID4 IV key. | ||
My program to dump EID4 AES-CBC-128 IV and key to PPU memory: | |||
<pre> | |||
< | |||
/* | /* | ||
* Dump EID4 IV and key to EA with MFC | * Dump EID4 IV and key to EA with MFC | ||
Line 127: | Line 119: | ||
bi $lr | bi $lr | ||
</pre> | </pre> | ||