Splice in cryptodev (this man page originated on openbsd where there is
no cryptodev module.) Should probably create a separate cryptodev man page (or a link to this one) but for now add enough so folks understand the relationship between the two. Prodded by: phk
This commit is contained in:
parent
016344807a
commit
4acf93a2f3
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=124594
@ -28,22 +28,28 @@
|
||||
.\"
|
||||
.\" $FreeBSD$
|
||||
.\"
|
||||
.Dd October 3, 2002
|
||||
.Dd January 16, 2004
|
||||
.Dt CRYPTO 4
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm crypto
|
||||
.Nm crypto ,
|
||||
.Nm cryptodev
|
||||
.Nd hardware crypto access driver
|
||||
.Sh SYNOPSIS
|
||||
.Cd device crypto
|
||||
.Cd device cryptodev
|
||||
.Sh DESCRIPTION
|
||||
The
|
||||
.Nm
|
||||
driver provides userland applications access to hardware crypto support
|
||||
via the kernel.
|
||||
driver provides a device-independent framework to support
|
||||
cryptographic operations in the kernel.
|
||||
The
|
||||
.Nm cryptodev
|
||||
driver provides userland applications access to this support
|
||||
through the
|
||||
.Pa /dev/crypto
|
||||
device node primarily operates in an
|
||||
device.
|
||||
This node primarily operates in an
|
||||
.Xr ioctl 2
|
||||
based model, permitting a variety of applications to query device capabilities,
|
||||
submit transactions, and get results.
|
||||
|
Loading…
Reference in New Issue
Block a user