Template talk:Metbootldr: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
: Those should've been done long ago, yes. But because this particular (abstracted) templated table is used by <!--// lets just say noobs :P that want to downgrade //-->non-devs too, it would be wise imo to relay that info to each loader section, [[Talk:Flash:bootldr]] & [[Talk:Flash:asecure loader]]. [[User:Euss|Euss]] | : Those should've been done long ago, yes. But because this particular (abstracted) templated table is used by <!--// lets just say noobs :P that want to downgrade //-->non-devs too, it would be wise imo to relay that info to each loader section, [[Talk:Flash:bootldr]] & [[Talk:Flash:asecure loader]]. [[User:Euss|Euss]] | ||
´ | ´ | ||
* this seems to be the most likely candidate for the crypto metldr/bootldr uses http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/proposedmodes/ | * this seems to be the most likely candidate for the crypto metldr/bootldr uses http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/proposedmodes/gcm/gcm-spec.pdf | ||
* to be confirmed... | * to be confirmed... | ||
Revision as of 22:35, 2 June 2016
Wouldn't it be wise to add the metldr/bl per revision keys (they stay the same per revision) ? I added the ones for the DECR-1000, it's visible in the edit if you want to have a look
It's located at header+0x04 the size itself is 0x0C (12 bytes)
Also for information purposes, the per console key is located at header+0x14 and is static per console, it's also 0x0C in size.
- Mathieulh
- Those should've been done long ago, yes. But because this particular (abstracted) templated table is used by non-devs too, it would be wise imo to relay that info to each loader section, Talk:Flash:bootldr & Talk:Flash:asecure loader. Euss
´
- this seems to be the most likely candidate for the crypto metldr/bootldr uses http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/proposedmodes/gcm/gcm-spec.pdf
- to be confirmed...