On Mon, Jul 1, 2019 at 4:11 PM Jouni Malinen <jkmali...@gmail.com> wrote:
> <snip> > > (1) Crypto-Binding TLV format for the cases where the negotiated TLS > cipher suite uses SHA256 (or SHA384, for that matter) instead of SHA-1 (and > I'd hope all deployments of TEAP would be recent enough to avoid use of > SHA-1..): > https://www.rfc-editor.org/errata/eid5768 > > > [Joe] I'd like to hear if anyone has an implementation, and how they implemented on a cipher suite that is not SHA-1. My feeling is that it would be better to make the TLV length variable with the hash length. However, I do not see why truncating would work as well. > > - Jouni > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www.ietf.org/mailman/listinfo/emu >
_______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
