5 Commits

Author	SHA1	Message	Date
Mark Murray	f544a52873	Module-ize the 'core' crypto stuff. This may still need to be compiled ... into the kernel by default (if required), but other modules can now depend() on this. Fix inter-module dependancy. Earlier version OK'ed by: sam	2002-10-16 14:31:34 +00:00
Mike Barcroft	2b7f24d210	Change iov_base's type from char *' to the standard void *'. All ... uses of iov_base which assume its type is `char *' (in order to do pointer arithmetic) have been updated to cast iov_base to `char *'.	2002-10-11 14:58:34 +00:00
Sam Leffler	1a91ccccc6	o split crypto_proc into two threads: one for processing requests and one ... for processing callbacks. This closes race conditions caused by locking too many things with a single mutex. o reclaim crypto requests under certain (impossible) failure conditions	2002-10-07 18:46:38 +00:00
Sam Leffler	b4c408e0fe	remove CIOGSSESSION (get software session); it was added only for testing	2002-10-07 18:37:31 +00:00
Sam Leffler	091d81d134	In-kernel crypto framework derived from openbsd. This facility provides ... a consistent interface to h/w and s/w crypto algorithms for use by the kernel and (for h/w at least) by user-mode apps. Access for user-level code is through a /dev/crypto device that'll eventually be used by openssl to (potentially) accelerate many applications. Coming soon is an IPsec that makes use of this service to accelerate ESP, AH, and IPCOMP protocols. Included here is the "core" crypto support, /dev/crypto driver, various crypto algorithms that are not already present in the KAME crypto area, and support routines used by crypto device drivers. Obtained from: openbsd	2002-10-04 20:31:23 +00:00