> On Sep 3, 2018, at 8:58 PM, Mark Andrews <ma...@isc.org> wrote: > > SHAKE128 does not meet these requirements. In OPENSSL it is only > available in pre-release code. It will be years before OPENSSL-1.1.1 > is the OPENSSL release for most operating systems. > > We (ISC) haven’t started working out what OPENSSL-1.1.1 breaks yet. > OPENSSL-1.1.0 broke lots of existing code. Lots of code required > re-writing to work with OPENSSL-1.1.0 as it broke backwards compatibility > with OPENSSL-1.0.x.
While I understand your point, OpenSSL 1.1.1 is the first release that will contain TLS 1.3. It is binary backward compatible with 1.1.0. Aside from our trivial use of SHAKE128, everyone is going to be upgrading to 1.1.1 as soon as possible to get TLS 1.3 support. See https://wiki.openssl.org/index.php/TLS1.3 > > Please pick hash algorithms that are already USED by DNS. The results > can be truncated if you are worried about space. > > And no it isn’t as easy as just calling OPENSSL. PKCS#11 providers > also need to support the hash algorithm. > Ok, thanks for this extra info. I will look into it. Tom _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
