Hacking Number of Switch Keys (Don't Ask For Them)

[shinyquagsire23]

They haven't leaked in full yet, but those are supposedly (unconfirmed) the first byte of each key.

The keys don't start with those bytes.

 

[SimonMKWii]

The keys don't start with those bytes.

Thanks for the confirmation!
4chan bullshit strikes again...

 

[TiMeBoMb4u2]

I have 18 key, what am I missing ?
here the keys a got:

master_key_00 = C2CXXXXXXXXXXXXXXXXXXXX
master_key_01 = 54EXXXXXXXXXXXXXXXXXXXX
master_key_02 = 4F6XXXXXXXXXXXXXXXXXXXX

package1_key_00 = F4EXXXXXXXXXXXXXXXXXXXX
package2_key_00 = A35XXXXXXXXXXXXXXXXXXXX
package2_key_01= A0DXXXXXXXXXXXXXXXXXXXX
package2_key_02 = 7E5XXXXXXXXXXXXXXXXXXXX

titlekek_source = 1EDXXXXXXXXXXXXXXXXXXXX
header_kek_source = 1F1XXXXXXXXXXXXXXXXXXXX
header_key_source = 5A3XXXXXXXXXXXXXXXXXXXX
package2_key_source = FB6XXXXXXXXXXXXXXXXXXXX
aes_kek_generation_source = 4D8XXXXXXXXXXXXXXXXXXXX
aes_key_generation_source = 874XXXXXXXXXXXXXXXXXXXX
key_area_key_application_source = 7F5XXXXXXXXXXXXXXXXXXXX
key_area_key_ocean_source = 327XXXXXXXXXXXXXXXXXXXX
key_area_key_system_source = 874XXXXXXXXXXXXXXXXXXXX

XCI Header Key = 01CXXXXXXXXXXXXXXXXXXXX
NCA Header Encryption Key = AEAXXXXXXXXXXXXXXXXXXXX

Are you talking about 20 keys including the master key 03 and 04 ?

I think the "XCI Header Key" is unique to each XCI.
It's located at 0x120:0x130 in every XCI file. It just needs to be reversed.
So, I wasn't counting that one.

Also, the "NCA Header Encryption Key" is commonly referred to as "header_key".

That should bring the total to seventeen (17), right?

If so, it looks like I'm missing:

package2_key_01
package2_key_02

 

[key1340]

There have been 13 keys leaked and you can generate 16 more keys from them taking the total to 29 keys.

The sha256 hashes from all 29 keys are here https://gist.github.com/nicoboss/967cd250d3969e1c4610c54e3186193b

All 29 keys are on the net and i have confirmed them with there sha256 hashes.

There are at least 6 more private keys that you can generate 10 more keys from to make 16 more keys needed.

 

[TiMeBoMb4u2]

There have been 13 keys leaked and you can generate 16 more keys from them taking the total to 29 keys.
The sha256 hashes from all 29 keys are here https://gist.github.com/nicoboss/967cd250d3969e1c4610c54e3186193b
All 29 keys are on the net and i have confirmed them with there sha256 hashes.
There are at least 6 more private keys that you can generate 10 more keys from to make 16 more keys needed.

I think the "leaked" number is now 15, since BBB posted the "master_key_01" and "master_key_02" with their "A.O.T. 2 (Attack on Titan 2)" release.

 

[key1340]

I think the "leaked" number is now 15, since BBB posted the "master_key_01" and "master_key_02" with their "A.O.T. 2 (Attack on Titan 2)" release.

No the leaked keys are

master_key_00
master_key_01
master_key_02
package1_key_00
package2_key_source
titlekek_source
aes_kek_generation_source
aes_key_generation_source
key_area_key_application_source
key_area_key_ocean_source
key_area_key_system_source
header_kek_source
header_key_source

The rest are all generated from them.

 

[tunip3]

I wish we cand decrypt ps4 keys too..

Oh I got em pm me

 

[TiMeBoMb4u2]

No the leaked keys are

master_key_00
master_key_01
master_key_02
package1_key_00
package2_key_source
titlekek_source
aes_kek_generation_source
aes_key_generation_source
key_area_key_application_source
key_area_key_ocean_source
key_area_key_system_source
header_kek_source
header_key_source

The rest are all generated from them.

Okay, so you're not counting "package2_key_00" and "header_key", because they are derivable, right?

 

[key1340]

Okay, so you're not counting "package2_key_00" and "header_key", because they are derivable, right?

Yes they are both derivable so i didn't count them.

 

[TiMeBoMb4u2]

Yes they are both derivable so i didn't count them.

Thanks, again. I clarified "leaked" vs "derivable" in the OP.

 

[pingtendo]

There have been 13 keys leaked and you can generate 16 more keys from them taking the total to 29 keys.

The sha256 hashes from all 29 keys are here https://gist.github.com/nicoboss/967cd250d3969e1c4610c54e3186193b

All 29 keys are on the net and i have confirmed them with there sha256 hashes.

There are at least 6 more private keys that you can generate 10 more keys from to make 16 more keys needed.

So 6 more private keys we don't know yet are:
master_key_03
master_key_04
package1_key_01
package1_key_02
package1_key_03
package1_key_04

and 10 more keys to generate are:
package2_key_03
package2_key_04
titlekek_03
titlekek_04
key_area_key_application_03
key_area_key_application_04
key_area_key_ocean_03
key_area_key_ocean_04
key_area_key_system_03
key_area_key_system_04

right?

 

[TiMeBoMb4u2]

So 6 more private keys we don't know yet are:
master_key_03
master_key_04
package1_key_01
package1_key_02
package1_key_03
package1_key_04

and 10 more keys to generate are:
package2_key_03
package2_key_04
titlekek_03
titlekek_04
key_area_key_application_03
key_area_key_application_04
key_area_key_ocean_03
key_area_key_ocean_04
key_area_key_system_03
key_area_key_system_04

right?

To my knowledge, this is correct.

 

[mariogamer]

Is it actually possible to derive the keys without the switch hardware? And how much time would be needed to do that? (Edit: thinking about that, it shouldn't tale that much time since it is onlye a derivation, but idk)

 

[TiMeBoMb4u2]

Is it actually possible to derive the keys without the switch hardware? And how much time would be needed to do that?

If you have a dump of the Switch archive 0100000000000819 and the master_key and package1_key for the version of the Switch from which the archive was obtained, you can find all the other key_sources.

 

[mariogamer]

If you have a dump of the Switch archive 0100000000000819 and the master_key and package1_key for the version of the Switch from which the archive was obtained, you can find all the other key_sources.

No I'm talking about derivable keys (eg. *_##keys) (except master and package1 keys)

 

[TiMeBoMb4u2]

No I'm talking about derivable keys (eg. *_##keys) (except master and package1 keys)

It's a bit complicated...

You need package1_key to decrypt package1, which contains the Secure_Monitor.bin. In there you'll find half the seeds, including the package2_key_source.

The master_key is then needed (with the package2_key_source) to decrypt the package2, which contains FS, where the other half of the seeds are located.

You can also find more information regarding the keys within SciresM's hactool GitHub here:
https://github.com/SciresM/hactool/blob/master/KEYS.md

 

[mariogamer]

Forget about it, I thought hactool wasn't generating them, but it does.

 

[TiMeBoMb4u2]

Forget about it, I thought hactool wasn't generating them, but it does (except package2, apparently)

Correct. To my knowledge, as long as you have the correct keys and key_sources, hactool is deriving other keys "on-the-fly".

 

[TiMeBoMb4u2]

After receiving permission from the GBAtemp Moderators (@porkiewpyne), I have restructured my OP and included the key hashes of the known keys. I hope this template will assist other users. Cheers!

 

[xXDungeon_CrawlerXx]

package1_key_03 = C32XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Sha256-Hash = 5f00a32111ce901b157db3b082d2756f2902830238d4e2c7a217cdaa5d512ba4