> On Aug 26, 2018, at 7:07 PM, Paul Vixie <p...@redbarn.org> wrote: > > Tom Pusateri wrote: >> >> There’s no attack vector here. And a collision would have to be >> another valid RR already in the database with the same owner name and >> class. This is literally impossible. Probably not even with md5! > > as i wrote when the discussion of catalog zone hashing got to this point, "if > collisions are impossible even with md5, then please use md5, and include a > security considerations paragraph or two as to how this is not a problem. for > that matter, if md4 or md3 will work, use those. unnec'y hash complexity is a > form of security theater." > > -- > P Vixie
You may be ok with that but no one from the security area will be. That’s just a fact of the times. The code in OpenSSL is identical no matter which hash you pick except for the hash name so it’s no more complex to implement. My approach was to pick the best hash available with a small output length. Thanks, Tom _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
