NAME
crypto —
hardware crypto access
driver
SYNOPSIS
pseudo-device crypto
[count]
DESCRIPTION
The crypto driver provides userland
applications access to hardware crypto support via the kernel. The
/dev/crypto device node primarily operates in an
ioctl(2) based model, permitting a variety of applications to query
device capabilities, submit transactions, and get results.
If count is given in the specification, and
is greater than 0, a maximum of one crypto device is
created.
The following
ioctl(2) calls apply only to the crypto
devices:
CIOCGSESSION- Set up a new crypto session for a new type of operation.
CIOCFSESSION- Free a previously established session.
CIOCCRYPT- Perform a crypto operation against a previously set up session.
FEATURES
Depending on hardware being present, the following symmetric and asymmetric cryptographic features are potentially available from /dev/crypto:
- CRYPTO_DES_CBC
- CRYPTO_3DES_CBC
- CRYPTO_BLF_CBC
- CRYPTO_CAST_CBC
- CRYPTO_MD5_HMAC
- CRYPTO_SHA1_HMAC
- CRYPTO_RIPEMD160_HMAC
- CRYPTO_MD5_KPDK
- CRYPTO_SHA1_KPDK
- CRYPTO_AES_CBC
- CRYPTO_AES_CTR
- CRYPTO_AES_XTS
- CRYPTO_ARC4
- CRYPTO_MD5
- CRYPTO_SHA1
- CRK_MOD_EXP
- CRK_MOD_EXP_CRT
- CRK_DSA_SIGN
- CRK_DSA_VERIFY
- CRK_DH_COMPUTE_KEY
FILES
- /dev/crypto
- crypto access device
SEE ALSO
hifn(4), lofn(4), noct(4), nofn(4), safe(4), ubsec(4), crypto(9)
HISTORY
The crypto driver appeared in
OpenBSD 3.0.