Age | Commit message (Collapse) | Author |
|
number of key bits is supplied.
Only AES and DES/3DES might fail.
ok and help markus@
|
|
This moves md5.c out of libkern and into sys/crypto where it belongs (as
requested by markus@). Note that md5.c is still mandatory (dev/rnd.c uses it).
Verified with IPsec + hmac-md5 and tcp md5sig. OK henning@ and hshoexer@
|
|
|
|
|
|
bandwidth of the kernel API). It's only available from userland and
then only if kern.cryptodevallowsoft=1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hacking at OpenBSD Crypto 2000 :-)
|
|
idea is to support various cryptographic hardware accelerators (which
may be (detachable) cards, secondary/tertiary/etc processors,
software crypto, etc). Supports session migration between crypto
devices. What it doesn't (yet) support:
- multiple instances of the same algorithm used in the same session
- use of multiple crypto drivers in the same session
- asymmetric crypto
No support for a userland device yet.
IPsec code path modified to allow for asynchronous cryptography
(callbacks used in both input and output processing). Some unrelated
code simplification done in the process (especially for AH).
Development of this code kindly supported by Network Security
Technologies (NSTI). The code was writen mostly in Greece, and is
being committed from Montreal.
|