| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: Doug Ambrisko" <ambrisko@verniernetworks.com>
|
|
|
|
| |
Submitted by: Doug Ambrisko" <ambrisko@verniernetworks.com>
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
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 *'.
|
|
|
|
|
|
| |
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
|
| |
|
|
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
|