Manual Reference Pages - SAFE (4)
- SafeNet crypto accelerator
To compile this driver into the kernel,
place the following lines in your
kernel configuration file:
.Cd device crypto
.Cd device cryptodev
.Cd device safe
Alternatively, to load the driver as a
module at boot time, place the following line in
driver supports cards containing SafeNet crypto accelerator chips.
driver registers itself to accelerate DES, Triple-DES, AES, MD5-HMAC,
SHA1-HMAC, and NULL operations for
On all models, the driver registers itself to provide random data to the
Periodically the driver will poll the hardware RNG and retrieve
data for use by the system.
If the driver detects that the hardware RNG is resonating with any local
signal, it will reset the oscillators that generate random data.
settings control this procedure:
specifies the time, in seconds, between polling operations,
specifies the number of 32-bit words to retrieve on each poll,
specifies the threshold for resetting the oscillators.
When the driver is compiled with
variables are provided for debugging purposes:
can be set to a non-zero value to enable debugging messages to be sent
to the console for each cryptographic operation,
is a write-only variable that can be used to force driver state to be sent
to the console.
Set this variable to
to dump the current state of the descriptor ring,
to dump the hardware DMA registers,
to dump the hardware interrupt registers.
driver supports cards containing any of the following chips:
| SafeNet 1141
The original chipset.
Supports DES, Triple-DES, AES, MD5, and SHA-1
symmetric crypto operations, RNG, public key operations, and full IPsec
| SafeNet 1741
A faster version of the 1141.
Public key support is not implemented.
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.