I have not seen any affirmed validation of this key. Did you decrypt it yourself?package1_key_03 = C32XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Sha256-Hash = 5f00a32111ce901b157db3b082d2756f2902830238d4e2c7a217cdaa5d512ba4
I have not seen any affirmed validation of this key. Did you decrypt it yourself?package1_key_03 = C32XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Sha256-Hash = 5f00a32111ce901b157db3b082d2756f2902830238d4e2c7a217cdaa5d512ba4
I have not seen any affirmed validation of this key. Did you decrypt it yourself?
Since I'm on 4.1, no.Have you done the same for package1_key_01 and package1_key_02?
master_key_03 = 84E0XXXXXXXXXXXXXXXXXXXXXXXXXXXX
SHA256(master_key_03) = 4f36c565d13325f65ee134073c6a578ffcb0008e02d69400836844eab7432754
Yep, that's 100% correct!Code:master_key_03 = 84E0XXXXXXXXXXXXXXXXXXXXXXXXXXXX SHA256(master_key_03) = 4f36c565d13325f65ee134073c6a578ffcb0008e02d69400836844eab7432754
Your package1_key_03 string appears to be correct starting with "C32", but your SHA256 hash does not comply with the standard binary hashing that has been used throughout.package1_key_03 = C32XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Sha256-Hash = 5f00a32111ce901b157db3b082d2756f2902830238d4e2c7a217cdaa5d512ba4
you mean those leaks are possibly, an inside job??"package1_key_00" was leaked at the beginning of January.
"header_key" was leaked sometime mid-January.
"master_key_00" was leaked at the beginning of February.
Others came after these.
Not sure. Used this to generate the Sha256-Hash: http://www.xorbin.com/tools/sha256-hash-calculator.Your package1_key_03 string appears to be correct starting with "C32", but your SHA256 hash does not comply with the standard binary hashing that has been used throughout.
You are using SHA256 "String" hashes. All other known SHA256 hashes have been posted as "Binary".Not sure. Used this to generate the Sha256-Hash: http://www.xorbin.com/tools/sha256-hash-calculator.
the last four Numbers/Letters are btw D8BC. Just to be sure.
EDIT:
Used another Calculator. This should be the correct Hash:
F5F1803511B5F1ECC4A1756C520FD506BD9F34BB64D90ECA0E8D41E2EE4284D6
You are using SHA256 "String" hashes. All other known SHA256 hashes have been posted as "Binary".
SOURCES:
sd_card_kek_source
sd_card_save_key_source
sd_card_nca_key_source
DERIVABLES:
sd_card_save_key
sd_card_nca_key
According to SciresM, they are used to decrypt content on the SD Card.which is the use for this ? sorry i am not programer
SciresM (on Discord) said:easiest way to find your sd card seed, btw:
-open up SYSTEM2 dump in hex editor
-open up sd:/Nintendo/Contents/private in a hex editor
-search for the bytes from that SD card file in SYSTEM2
-sd seed is the 16 bytes following it
; The vulnerable NVIDIA Tegra X1 bootROM.
; NVIDIA Tegra X1 bootROM (un-ipatched)
;
; SHA256(tx1_bootrom_file) = 1C629AF8A34ADF21771630822A77FF78F57D0BA3E4953D96F0F68E5AB2B38DEC
This really isn't a "Switch Key", so I won't be posting it to the OP.
However, this information may be of use to those of you interested.
Code:; The vulnerable NVIDIA Tegra X1 bootROM. ; NVIDIA Tegra X1 bootROM (un-ipatched) ; ; SHA256(tx1_bootrom_file) = 1C629AF8A34ADF21771630822A77FF78F57D0BA3E4953D96F0F68E5AB2B38DEC
But have you figured out what the leaked '20byte' F8 00 00 .. .. .. thingie was at the end of the two posts? -- a Key? or just a SHA1 hash? but for what? -- if you do find out, send me a PM. -- Thanks!