Re: SHA3 implementation in src

On Mon, Mar 07, 2016 at 03:21:56PM +0000, Taylor R Campbell wrote:
> Another possibility would be to use different libc symbols for our
> versions that are guaranteed not to collide with OpenSSL's, say
> _netbsd_SHA3_*.  This won't work retroactively for the sha1 and sha2
> functions, but it would have worked if we had done it up front.
> 
> However, I'm not totally clear on the severity or breadth of the
> fallout, so I'll defer to someone who has experience with it.  joerg?

That's reasonable. You can even use the asm rename to expose them under
the unprefixed name.

Joerg