SODA Noriyuki wrote:

> Hmm, if the functions will be shared by the kernel and standalone
> programs, isn't libkern the right place to put it in?
> 
> How about moving sys/crypto functions to sys/libkern, instead of vice
> versa?

After some discussion, this seems to be the right decision.

Apparently when adding SHA2 and RMD160 to the kernel this was not
thought through, and they were placed, perhaps wrongly, in sys/crypto.

sys/crypto was used a while ago to allow easy separation between the
US and non-US trees due to US crypto export laws. Now, there is no
longer a requirement for this separation.

Since libkern is used in the kernel as libc is used in userland, we
might consider moving the SHA2 and RMD160 hashing code to it, as you
suggested, instead of doing it the other way round. We'll also
document decisions to avoid future confusion. :)

Thanks,

-e.

-- 
Elad Efrat
PGP Key ID: 0x666EB914