Per Console Keys: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
(→‎per_console_root_key_1 / EID_root_key: You cannot derive EID_root_key from going backwards from a derived key.)
No edit summary
Line 1: Line 1:
==per_console_root_key_0==
== per_console_root_key_0 ==


*bootldr and metldr are decrypted with this key. See also [[Boot Order]]
* bootldr and metldr are decrypted with this key. See also [[Boot Order]].
*might be obtained with per_console_root_key_1 ? '''(largely speculative, not nec. true - need more looked into, only based on the behavior of the other derivatives known to be obtained through AES)'''
* Might it be obtained with per_console_root_key_1 ? It need more looked into. It might be the case, based on the behavior of the other derivatives known to be obtained through AES.


==per_console_root_key_1 / EID_root_key==
== per_console_root_key_1 (EID_root_key) ==


*derived from per_console_key_0
* Derived from per_console_key_0
*stored inside metldr
* Stored inside metldr
*copied to sector 0 by metldr
* Copied to sector 0 by metldr
*cleared by isoldr
* Cleared by isoldr
*Used to decrypt part of the EID
* Used to decrypt part of the EID
*Used to derive further keys ''(per_console_key_0 is not the key which will be derived, but is the key which has derived per_console_key_1)''
* Used to derive further keys
*can be obtained with a modified isoldr that dumps it
* Can be obtained with a modified isoldr that dumps it


=== Obtaining It ===
=== Obtaining It ===


Launch the patched isoldr with your prefered method, let it be Option 1, or Option 2...
Launch the patched isoldr with your preferred method, let it be Option 1, or Option 2...


==== Option 1 - Dumper Kernel Module ====
==== Option 1 - Dumper Kernel Module ====


*modify glevands spp_verifier_direct to dump the mbox to wherever_you_want  
* Modify glevand's spp_verifier_direct to dump the mbox to wherever_you_want.
'''http://pastebin.com/uTBbnC9B'''<-needs to be edited further
* http://pastebin.com/uTBbnC9B <- needs to be edited further


<pre>
<pre>
Line 33: Line 33:


==== Option 2 - Dumper Payload ====
==== Option 2 - Dumper Payload ====
*http://pastebin.com/YwDKqgTj <!--// http://pastie.org/pastes/2101977 //-->


*patched isoldr to dump it
* http://pastebin.com/YwDKqgTj <!--// http://pastie.org/pastes/2101977 //-->
'''*DO NOT CREATE AN MFW USING THIS IT WOULD BRICK PS3'''
*patched isoldr: http://www.wupload.com/file/1153650416/dump_eid_root_key.self


*this can be loaded as the payload stage2 in the payload marcan used to load linux
'''*DO NOT CREATE AN MFW USING THIS IT WOULD BRICK'''
* Patched isoldr to dump it: http://www.wupload.com/file/1153650416/dump_eid_root_key.self <- dead link
 
* This can be loaded as the payload stage2 in the payload marcan used to load linux.
** http://marcansoft.com/blog/2010/10/asbestos-running-linux-as-gameos/
** http://marcansoft.com/blog/2010/10/asbestos-running-linux-as-gameos/
** http://git.marcansoft.com/?p=asbestos.git
** http://git.marcansoft.com/?p=asbestos.git


*this can also be loaded as with lv2patcher and payloader3
* This can also be loaded as with lv2patcher and payloader3.
**payloader3.git
** payloader3.git <- ?dead link ?


==== Comments ====
==== Comments ====
*What this selfs do is dump your '''ISOLATED SPU''' LS through your mbox, so you only need a way to cach this info with '''PPU code in lv2 enviroment''' aka a '''dongle payload''' or '''linux kernel'''
*This has been tested and proven to work on 3.55 MFW
*In the dump the remaining dump is the metldr clear code. metldr clears itself and all the registers an jumps to isoldr.
*Overwritting that code lets you dump your key + metldr
*Consider that per_console_key_1 and per_console_key_n are in fact still in need decryption.
*per_console_key_0 particularly needs to be dumped once revived from per_console_key_1.


==per_console_root_key_2 / EID0_key ==
* What these SELFs do is dump the PS3 '''ISOLATED SPU''' LS through mbox, so you only need a way to catch this data with PPU code in lv2 environment aka a dongle payload or linux kernel.
* This has been tested and proven to work on 3.55 MFW.
* In the dump the remaining dump is the metldr clear code. metldr clears itself and all the registers then jumps to isoldr.
* Overwritting that code lets you dump your key + metldr.
 
== per_console_root_key_2 (EID0_key) ==
 
=== Obtaining It ===
 
==== Using the reversed code ====


*this key can be obtained through AES from EID_root_key
* This key can be obtained through AES from eid_root_key.
**EID0_key can be gotten this way through a program such as openssl, using the following command once installed:
* The algorithm is located in isoldr.
* EID0_key can be gotten through a program such as openssl, using the following command (once installed):
<pre>
<pre>
openssl aes-256-cbc -e -in eid0_key_seed -out eid0_enc_seed -nosalt -K (isoldr key) -iv (isoldr RIV) -p -nopad
openssl aes-256-cbc -e -in eid0_key_seed -out eid0_enc_seed -nosalt -K (isoldr key) -iv (isoldr RIV) -p -nopad
</pre>
</pre>


 
See [[Seeds]].
eid0_key_seed:
ABCAAD1771EFABFC2B921276FAC2130C
37A6BE3FEF82C79F3BA5733FC35A690B
08B358F970FA16A3D2FFE2299E841EE4
D3DB0E0C9BAEB51BC7DFF10467472F85


==== Using anergistics (advanced users) ====


*EID can be partially decrypted by setting this key in anergistics and fireing aim_spu_module.self


EID0 can be decrypted by setting EID0_key in anergistics and fireing aim_spu_module.self:
* Load aim_spu_module.self + EID0 + EID0_key in anergistics -> decrypted EID0.
* This [http://pastebin.com/xdPYgqXG <!--// http://pastie.org/2000330 //--> code] decrypts EID0 on PC.
* The prerequisites are:
** Dump EID0 from your PS3.
** Dump EID0_key from your PS3 and put it in the code above where the key (eid_mkey?) is needed.
** Load all of them in anergistic.


Using similar steps, you can provide eid_root_key and obtain EID0_key:
* EID0_key can be obtained with eid_root_key directly by letting isoldr apply the algorithm in anergistic.
* It needs modifing anergistic to feed isoldr with eid_root_key.
* Patched aim_spu_module to dump EID0_Key:
'''*DO NOT CREATE AN MFW USING THIS IT WOULD BRICK'''
** http://dl.dropbox.com/u/35197530/aim.self <- dead link


*Load aim_spu_module.self + EID0 + EID0_key in anegistics = decrypted EID0
== per_console_root_key_n ==
*[http://www.ps3devwiki.com/files/devtools/PerConsoleKeys/pastie-2000330/ This code] is to decrypt your EID0 on your PC http://pastebin.com/xdPYgqXG <!--// http://pastie.org/2000330 //-->
**The prerequisites are:
***dump your EID0 from your ps3 and save it in the same folder as EID0
***dump your EID0_key from your ps3 and put it on the code above where the key is needed
***load all of them in anergistic


*EID0_key could also be obtained with '''EID_root_key''' directly in the following manners:
These are further derivations of the per_console_key_1 (EID_root_key).
**knowing the algorithm (located in isoldr) and applying it to the EID_root_key
**let isoldr apply that algorithm directly in anergistic
***the process is exactly as the one above (modifing anergistic to feed isoldr with EID_root_key


See [https://github.com/zecoxao/ps3_decrypt_tools/ ps3_decrypt_tools by naehrwert, zecoxao and al.].


=== Obtaining It ===
== cVTRM ==


*patched aim_spu_module to dump it
SRK (Secret or Syscon Root Key - root hash secret (hsec)) (derivation from per console key?) is stored in Syscon along with SRH (Secret or Syscon Root Hash). SRK is used as HMAC hash to authenticate cVTRM data from flash. SRH is a hash of cVTRM data. SRH is computed at runtime and compared with SRH from Syscon.
'''*DO NOT CREATE AN MFW USING THIS IT WOULD BRICK'''
**http://www.multiupload.com/1XUOOYS9I0
**http://dl.dropbox.com/u/35197530/aim.self (to be verified. if it is the same file, i'll upload it again to mediafire
**http://www.ps3devwiki.com/files/devtools/PerConsoleKeys/aim.self


==per_console_root_key_n==
You can fetch SRH with VTRM or SCM utilities from glevand's ps3-vuart-tools (you need to add the function to the tools to do so) or from GameOS directly if you do some patches at hypervisor level.


These are further derivations of the per_console_key_1/EID_root_key
cVTRM uses SysCon Isolated Module to do all the cryptographic operations. It uses AES-CBC-128 to encrypt data. It seems like key is fetched from encrypted key table in Syscon (related to EID1?). Also this key can be computed using AES-XTS-128. IV contains all zeroes. Data and tweak keys for XTS are computed from eid_root_key using seeds from SysCon Isolated Module.


==cVTRM==
Here is an example of decrypted cVTRM blocks:
 
'''SRK''' ('''root hash secret (hsec)''') (derivation from per console key?) is stored at '''Syscon''' along with '''SRH''' ('''root hash'''). SRK is used as HMAC hash to authenticate '''cVTRM''' data at flash, SRH is a hash of cVTRM data, it computed at runtime and compared with SRH from Syscon. You can fetch it with VTRM or SCM utilities from glevand's '''ps3-vuart-tools''' (you need to add the function to the tools to do so) or from GameOS directly if you do some patches at hypervisor level.


cVTRM uses SC isolated module to do all cryptographic operations. It uses AES-CBC-128 to encrypt data; seems like key is fetched from encrypted key table at Syscon (related to EID1?). Also this key can be computed using AES-XTS-128, IV contains all zeroes. Data and tweak keys for XTS are computed from EID root key using seeds from SC isolated module.
Here is an example of decrypted cVTRM blocks:
  1B68B7B67048454E863ECA0665EFB086  1B68B7B67048454E863ECA0665EFB08670F3EADB (Drive Revocation List Hash)
  1B68B7B67048454E863ECA0665EFB086  1B68B7B67048454E863ECA0665EFB08670F3EADB (Drive Revocation List Hash)
  70F3EADB96791F41F9A76F4D895DD582  96791F41F9A76F4D895DD5820DB108EC03D19250 (Content Revocation List Hash)
  70F3EADB96791F41F9A76F4D895DD582  96791F41F9A76F4D895DD5820DB108EC03D19250 (Content Revocation List Hash)
Line 126: Line 122:
  00000000000000000000000000000000
  00000000000000000000000000000000


https://dl.dropboxusercontent.com/u/35197530/zip/ps3linux-ps3vuart-tools.zip here's a link with the added functions. try to test it and report if it works :)
* [https://dl.dropboxusercontent.com/u/35197530/zip/ps3linux-ps3vuart-tools.zip DEAD LINK] Here's a link with the added functions. Please test it and report if it works :)
 
==Documentation==
 
http://polarssl.org/trac/browser/trunk/library/aes.c




{{Reverse engineering}}<noinclude>[[Category:Main]]</noinclude>
{{Reverse engineering}}<noinclude>[[Category:Main]]</noinclude>

Revision as of 01:59, 26 May 2020

per_console_root_key_0

  • bootldr and metldr are decrypted with this key. See also Boot Order.
  • Might it be obtained with per_console_root_key_1 ? It need more looked into. It might be the case, based on the behavior of the other derivatives known to be obtained through AES.

per_console_root_key_1 (EID_root_key)

  • Derived from per_console_key_0
  • Stored inside metldr
  • Copied to sector 0 by metldr
  • Cleared by isoldr
  • Used to decrypt part of the EID
  • Used to derive further keys
  • Can be obtained with a modified isoldr that dumps it

Obtaining It

Launch the patched isoldr with your preferred method, let it be Option 1, or Option 2...

Option 1 - Dumper Kernel Module

insmod ./spp_verifier_direct.ko
cat metldr > /proc/spp_verifier_direct/metldr
cat dump_eid_root_key.self > /proc/spp_verifier_direct/isoldr
echo 1 > /proc/spp_verifier_direct/run
cat /proc/spp_verifier_direct/debug
hd /ls.bin | less

Option 2 - Dumper Payload

*DO NOT CREATE AN MFW USING THIS IT WOULD BRICK

  • This can also be loaded as with lv2patcher and payloader3.
    • payloader3.git <- ?dead link ?

Comments

  • What these SELFs do is dump the PS3 ISOLATED SPU LS through mbox, so you only need a way to catch this data with PPU code in lv2 environment aka a dongle payload or linux kernel.
  • This has been tested and proven to work on 3.55 MFW.
  • In the dump the remaining dump is the metldr clear code. metldr clears itself and all the registers then jumps to isoldr.
  • Overwritting that code lets you dump your key + metldr.

per_console_root_key_2 (EID0_key)

Obtaining It

Using the reversed code

  • This key can be obtained through AES from eid_root_key.
  • The algorithm is located in isoldr.
  • EID0_key can be gotten through a program such as openssl, using the following command (once installed):
openssl aes-256-cbc -e -in eid0_key_seed -out eid0_enc_seed -nosalt -K (isoldr key) -iv (isoldr RIV) -p -nopad

See Seeds.

Using anergistics (advanced users)

EID0 can be decrypted by setting EID0_key in anergistics and fireing aim_spu_module.self:

  • Load aim_spu_module.self + EID0 + EID0_key in anergistics -> decrypted EID0.
  • This code decrypts EID0 on PC.
  • The prerequisites are:
    • Dump EID0 from your PS3.
    • Dump EID0_key from your PS3 and put it in the code above where the key (eid_mkey?) is needed.
    • Load all of them in anergistic.

Using similar steps, you can provide eid_root_key and obtain EID0_key:

  • EID0_key can be obtained with eid_root_key directly by letting isoldr apply the algorithm in anergistic.
  • It needs modifing anergistic to feed isoldr with eid_root_key.
  • Patched aim_spu_module to dump EID0_Key:

*DO NOT CREATE AN MFW USING THIS IT WOULD BRICK

per_console_root_key_n

These are further derivations of the per_console_key_1 (EID_root_key).

See ps3_decrypt_tools by naehrwert, zecoxao and al..

cVTRM

SRK (Secret or Syscon Root Key - root hash secret (hsec)) (derivation from per console key?) is stored in Syscon along with SRH (Secret or Syscon Root Hash). SRK is used as HMAC hash to authenticate cVTRM data from flash. SRH is a hash of cVTRM data. SRH is computed at runtime and compared with SRH from Syscon.

You can fetch SRH with VTRM or SCM utilities from glevand's ps3-vuart-tools (you need to add the function to the tools to do so) or from GameOS directly if you do some patches at hypervisor level.

cVTRM uses SysCon Isolated Module to do all the cryptographic operations. It uses AES-CBC-128 to encrypt data. It seems like key is fetched from encrypted key table in Syscon (related to EID1?). Also this key can be computed using AES-XTS-128. IV contains all zeroes. Data and tweak keys for XTS are computed from eid_root_key using seeds from SysCon Isolated Module.

Here is an example of decrypted cVTRM blocks: 

1B68B7B67048454E863ECA0665EFB086  1B68B7B67048454E863ECA0665EFB08670F3EADB (Drive Revocation List Hash)
70F3EADB96791F41F9A76F4D895DD582  96791F41F9A76F4D895DD5820DB108EC03D19250 (Content Revocation List Hash)
0DB108EC03D192500000000000000000
00000000000000000000000000000000

00000001000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000

087E91AEFFB8E66A0000000000000000  6AE6B8FFAE917E08 (PSN) Account ID
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000

00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
  • DEAD LINK Here's a link with the added functions. Please test it and report if it works :)


General
Hypervisor
Services
Plugin
Interfaces
ap_plugin · audioplayer_plugin · audiop_plugin_dummy · audiop_plugin_mini · auth_plugin · autodownload_plugin · autoupdateconf_plugin · avc_plugin · avc_util · avc2_game_plugin · avc2_game_video_plugin · avc2_text_plugin · bdp_disccheck_plugin · bdp_plugin · bdp_storage_plugin · campaign_plugin · category_setting_plugin · comboplay_plugin · custom_render_plugin · data_copy_plugin · deviceconf_plugin · dlna_plugin · download_plugin · dtcpip_util · edy_plugin · esehttp · eseibrd · eseidle · eselock · eula_cddb_plugin · eula_hcopy_plugin · eula_net_plugin · explore_plugin · explore_plugin_ft · explore_plugin_game · explore_plugin_np · filecopy_plugin · friendim_plugin · friendml_plugin · friendtrophy_plugin · game_ext_plugin · game_indicator_plugin · game_plugin · gamedata_plugin · gamelib_plugin · gameupdate_plugin · hknw_plugin · idle_plugin · impose_plugin · kensaku_plugin · msgdialog_plugin · mtpinitiator_plugin · musicbrowser_plugin · nas_plugin · netconf_plugin · newstore_plugin · np_eula_plugin · np_matching_plugin · np_multisignin_plugin · np_sns_plugin · npsignin_plugin · np_trophy_ingame · np_trophy_plugin · osk · oskfullkeypanel · oskpanel · pesm_plugin · photo_network_sharing_plugin · photolist_plugin · photoviewer_plugin · playlist_plugin · poweroff_plugin · premo_plugin · premo_game_plugin · print_plugin · profile_plugin · ps3_savedata_plugin · ps3_savedata_plugin_game · ps3_savedata_plugin_psp · rec_plugin · regcam_plugin · remotedownload_plugin · sacd_plugin · scenefolder_plugin · screenshot_plugin · software_update_plugin · soundvisualizer_plugin · strviewer_plugin · sysconf_plugin · system_plugin · thumthum_plugin · upload_util · user_info_plugin · user_plugin · videodownloader_plugin · videoeditor_plugin · videoplayer_util · videoplayer_plugin · vmc_savedata_plugin · wboard_plugin · webbrowser_plugin · webbrowser_service · webrender_plugin · xai_plugin · xmb_ingame · xmb_plugin
Emulation
Extended
features
Online
Hardware
SC
CELL
RAM
SB
HDD
BD
Tools
Strings
files
dumps
Reference
Keys & Seeds
Retrieved from "http://www.psdevwiki.com/ps3/index.php?title=Per_Console_Keys&oldid=56263"