[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AES Key Integrity

On Tue, 26 Jun 2001, Chris Trobridge wrote:

 > It has just occurred to me that I've not noticed any references to a
 > standard integrity mechanism for AES.
 >
 > Will there be one?
 >
 > DES has parity, but a CRC would be better.
 >
 > As crypto gets (theoretically) stronger issues like reliability become much
 > more important.

This is an important issue, but it does not (and should not) depend on the
concrete algorithm like AES. The subscribers from NIST to this list might
want to consider adopting a standard for storing cryptographic keys (of
any algorithm) for increasing reliability. Of course, standard here is
mainly needed for interoperability: All you need is an error-correcting
code (ECC) together with an optional (keyed?) hash. (Unkeyed hash does not
really seem to be necessary if one already employes an ECC.) For most of
the purposes a very simple ECC like Hamming code is good enough.

Helger
PS What a nice scary signature...

 > -----------------------------------------------------------------------------------------------------------------
 > The information contained in this message is confidential and is intended
 > for the addressee(s) only.  If you have received this message in error or
 > there are any problems please notify the originator immediately.  The
 > unauthorized use, disclosure, copying or alteration of this message is
 > strictly forbidden. Baltimore Technologies plc will not be liable for direct,
 > special, indirect or consequential damages arising from alteration of the
 > contents of this message by a third party or as a result of any virus being
 > passed on.
 >
 > In addition, certain Marketing collateral may be added from time to time to
 > promote Baltimore Technologies products, services, Global e-Security or
 > appearance at trade shows and conferences.
 >
 > This footnote confirms that this email message has been swept by
 > Baltimore MIMEsweeper for Content Security threats, including
 > computer viruses.
 >
References: