Re: SHA-3 in libc

[christos%astron.com@localhost (Christos Zoulas)]

In article <20141212204130.CA2AD604EC%jupiter.mumble.net@localhost>,
Taylor R Campbell  <campbell+netbsd-tech-userlevel%mumble.net@localhost> wrote:
>-=-=-=-=-=-
>
>The attached patch implements SHA3_224/256/384/512_Init/Update/Final
>following the similar sha2, sha1, md5, &c., APIs in libc.
>
>I propose to include these in libc and pull them up to netbsd-7,
>before the NIST SHA-3 draft is finalized, so that the symbols will be
>available in NetBSD 7's libc for applications to use later on without
>the trouble of adding symbols to libc in, e.g., NetBSD 7.1 once the
>draft is finalized.
>
>The man page will include a stern warning that the standard is a draft
>and may change, which we can remove when it is finalized.  If it does
>change before finalization, we can always pull up the change.  But I
>think it is unlikely to change at this point.
>
>Comments?

What would be the plan if the standard changes, and the functions are
made to compute different output? How are we going to recognize good
vs. broken versions of the functions.

christos