> That code does however, know which output values will > be public and which not. For me, that implies that any good separation > scheme applied within the TLS code that differentiates between public and > non public outputs is a good plan.
Agreed.
/r$, who is moving OpenSSL to DRBG AES128-ctr, and hopefully adding two
instances :)
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
