Re: [OSPF] OSPF HMAC Cryptographic Authentication

Manav:

>
=> RFC 2104 has the C code that allows the text being hashed to be of
an arbitary =length; the only restriction imposed is that the length
must be a multiple of 8 bits =(octet). If you look at
draft-eastlake-sha2-02.txt then it allows the text to be =hashed to
contain an arbitary number of bits.

Its been a long time since i read 2104 and i remembered that there
used to be some limitation. I was under the impression that it only
worked for a fixed length of input text T. Clearly, I was mistaken.

=>
=> Similarly, the code in RFC 3174 is a "byte-level"implementation.
The same draft =allows the text to be of an arbitary length. It adds
to the RFC 3174 API an =additional call,
=> SHA1FinalBits(), that lets the remaining bits to be added to the hash.
=>
=> I would prefer to refer to this draft as it (i) has full support
for all the SHA2 =algorithms and (ii) adds HMAC support for both SHA1
and SHA2 algorithms.

I am okay as long as you reference some document for HMAC and SHA algorithms.

Phil

=>
=> Thanks,
=> Manav
=>

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf