5 Commits

Author	SHA1	Message	Date
pjd	f055dbf32b	- Replace COPYDATA() and COPYBACK() macros with crypto_copydata() and ... crypto_copyback() functions. - Add crypto_apply() function. This will allow for more code simplification.	2006-06-04 22:15:13 +00:00
pjd	0e3d5d76cb	- Implement cuio_apply(), an equivalent to m_apply(9). ... - Implement CUIO_SKIP() macro which is only responsible for skipping the given number of bytes from iovec list. This allows to avoid duplicating the same code in three functions. Reviewed by: sam	2006-05-17 17:56:00 +00:00
imp	f0bf889d0d	/* -> /*- for license, minor formatting changes	2005-01-07 02:29:27 +00:00
obrien	74603d4bb9	Use __FBSDID().	2003-06-11 05:57:50 +00:00
sam	91416784e4	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