Editing Template talk:Metbootldr

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 <!--// 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]] &amp; [[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/gcm/gcm-spec.pdf
<pre>
Inputs and Outputs
GCM has two operations, authenticated encryption and authenticated decryption. The authenticated
encryption operation has four inputs, each of which is a bit string:
•	 A secret key K, whose length is appropriate for the underlying block cipher.
•	 An initialization vector IV , that can have any number of bits between 1 and 264. For a fixed
value of the key, each IV value must be distinct, but need not have equal lengths. '''96-bit
IV values can be processed more efficiently, so that length is recommended for situations in
which efficiency is critical.'''
•	 A plaintext P, which can have any number of bits between 0 and 239 − 256.
•	 Additional authenticated data (AAD), which is denoted as A. This data is authenticated, but
not encrypted, and can have any number of bits between 0 and 264.
</pre>