I guess I'll leaving this here, too:
I added support to read the SEEPROM data using code from MINI, but for some weird reason it doesn't work under vWii (a friend of mine already confirmed me this). Well, I guess it doesn't really matter... The Korean Key is publicly available, and the application is still creating a hexdump of the device.cert from the console (that does not fail), which actually contains most, if not all, of the usable information from the SEEPROM.
OTP access works perfectly, according to him.
Some additional info, for those who are interested:
- NG Signature (ng_sig): 60 bytes, located @ offset 0x4 in the device certifcate.
- NG Key ID (ng_key_id): 4 bytes, located @ offset 0x104 in the device certificate.
EDIT (12/28/2012): Fixed a
very silly bug that prevented the Korean Key to be displayed even it is was read properly from the SEEPROM.
I also added a small vWii check using ES_GetStoredTMDSize to read the length of the IOS512 TMD. If it fails to retrieve the TMD, it will return a false value and the application will work as it should; otherwise, the SEEPROM access will be disabled and the application will go straight to the OTP keys, instead of displaying that *annoying* error.
UPDATE (08/11/2013): Links updated on request. Thanks to TheChield for letting me know the Dropbox links are down.