Talk:Ticket: Difference between revisions
| Line 11: | Line 11: | ||
<b>Time enable</b> | <b>Time enable</b> | ||
There is a bit of an oddity about the 'time enable' field in that it seems to occupy 4 bytes while the value it affects only occupies 2 - can someone confirm that it is correct. An older revision had the "seconds" field as 4 bytes. | There is a bit of an oddity about the 'time enable' field in that it seems to occupy 4 bytes while the value it affects only occupies 2 - can someone confirm that it is correct. An older revision had the "seconds" field as 4 bytes. | ||
Just investigated the history and seems that an error was introduced when the end locations were included and the end padding displayed. A 4 byte field for seconds was shown as only occupying 2 bytes in the memory map. | |||
I changed the end locations and offsets of the seconds and final padding to correct. | |||
Revision as of 01:23, 23 December 2008
Meaning of first field
I believe 0x10001 is the exponent part of the RSA key (65537 is a common exponent for public keys), not a signature type.
TO CONFIRM: xt5 has said on HackMii that offset 0x1F1, with a value of 1, is used in Korean Wiis to use a different common key. Can someone confirm/update?
Yes this difference is notable between Korean and non-Korean update partition, this should be the marker --moquette 06:20, 30 August 2008 (UTC)
Time enable There is a bit of an oddity about the 'time enable' field in that it seems to occupy 4 bytes while the value it affects only occupies 2 - can someone confirm that it is correct. An older revision had the "seconds" field as 4 bytes.
Just investigated the history and seems that an error was introduced when the end locations were included and the end padding displayed. A 4 byte field for seconds was shown as only occupying 2 bytes in the memory map.
I changed the end locations and offsets of the seconds and final padding to correct.