| Re: EAP Key Management Framework (FYI) | <– Date –> <– Thread –> |
|
From: Jari Arkko (jari.arkko |
|
| Date: Fri, 26 Aug 2005 08:38:17 -0400 (EDT) | |
t.otto [at] sharevolution.de wrote:
--Jari
The non-public IV is derived from the secret keying material.
In NIST SP 800-56 however one find in section 5.8, Key Derivation Functions,
that "the output from a KDF shall only be used for secret keying material, such as a symmetric key used for data encryption or message integrity, [...]
Non-secret keying material (such as a non-secret initialization vector)
shal not be generated using the shared secret".
I am not sure, shouldn`t the EAP key management better comply with NIST
recommendations?
It would seem that this would only be a problem if the IV were actually used somewhere in a public manner.
Given that the use of the IV is already deprecated, I wonder if we should take this depracation even further and state that this value is reserved and must not be used for any purpose.
--Jari
-
EAP Key Management Framework (FYI) t . otto, August 26 2005
- Re: EAP Key Management Framework (FYI) Jari Arkko, August 26 2005
Results generated by Tiger Technologies using MHonArc.