-
Notifications
You must be signed in to change notification settings - Fork 12
Keyform.vb Issues #4
Description
- Contents of my keys.dat are as follows... so you can see how if someone manually had entered the information, it most likely won't match what you are expecting, might want to test/verify the hash of the substring you load in? Might just create a hash array and compare the ones you import then put them in the right place based on the hash or get rid of them.
master_key_00 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
master_key_01 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
master_key_02 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
master_key_03 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
package2_key_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
titlekek_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
aes_kek_generation_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
aes_key_generation_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
key_area_key_application_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
key_area_key_ocean_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
key_area_key_system_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
header_kek_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
header_key_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
package1_key_00 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
package1_key_03 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
Might want to consider using another font or equalize the spacing between characters, because even though most of the keys are the same number of hex digits, each key look like different lengths and it might concern people...
-
What if someone has a master key 4? There is a space for it, but no import/check, might cause issues down the road...
-
Oh man, I hit the question mark, then I hit save, it overwrote my keys :( Thankfully I made a backup :P
-
Ah crap, the Open button doesn't do anything, guess I gotta put the file back in the directory...