Defining the interface in terms of char * means most callers are
required to cast their pointers, which is ugly and possibly error
prone. accidentally casting an int to a pointer, for example, instea

Defining the interface in terms of char * means most callers are
required to cast their pointers, which is ugly and possibly error
prone. accidentally casting an int to a pointer, for example, instead
of the address of the int. implicit void * casting is safer.

This updates the kernel hash interfaces to use void *. Similar changes
are possible for userland. I think it's safe, but there may be some
peculiar source compatbility issues there, so let's just do the kernel
first.
ok dlg millert

show more ...

Make the hmac ipad/opad globals "const" and fixup the crypto functions
to match.

ok deraadt@

Some KNF, made bit count u_int64_t instead of u_int32_t (similar to libc).
Added constants for buffer lengths.

ok millert@

First round of __P removal in sys

better indent for easier searching

move crypto code