Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
SAFE(4)			 BSD Kernel Interfaces Manual		       SAFE(4)

NAME
     safe -- SafeNet crypto accelerator

SYNOPSIS
     device safe

     sysctl hw.safe.debug
     sysctl hw.safe.rnginterval
     sysctl hw.safe.rngbufsize
     sysctl hw.safe.rngmaxalarm

DESCRIPTION
     The safe 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, pub-
			 lic key operations, and full IPsec packet processing.

	   SafeNet 1741	 A faster version of the 1141.

     The safe driver registers itself to accelerate DES, Triple-DES, AES,
     MD5-HMAC, SHA1-HMAC, and NULL operations for ipsec(4) and crypto(4).

     On	all models, the	driver registers itself	to provide random data to the
     random(4) subsystem.  Periodically	the driver will	poll the hardware RNG
     and retrieve data to 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.  Three sysctl settings control
     this procedure: hw.safe.rnginterval specifies the time, in	seconds, be-
     tween polling operations, hw.safe.rngbufsize specifies the	number of
     32-bit words to retrieve on each poll, and	hw.safe.rngmaxalarm specifies
     the threshold for reseting	the oscillators.

     When the driver is	compiled with SAFE_DEBUG defined, two sysctl variables
     are provided for debugging	purposes: hw.safe.debug	can be set to a	non-
     zero value	to enable debugging messages to	be sent	to the console for
     each cryptographic	operation.  hw.safe.dump is a write-only variable that
     can be used to force driver state to be sent to the console.  Set this
     variable to ring to dump the current state	of the descriptor ring,	to dma
     to	dump the hardware DMA registers, or to int to dump the hardware	inter-
     rupt registers.

SEE ALSO
     crypt(3), crypto(4), intro(4), ipsec(4), random(4), crypto(9)

BUGS
     Public key	support	is not implemented.

BSD				 May 30, 2002				   BSD

NAME | SYNOPSIS | DESCRIPTION | SEE ALSO | BUGS

Want to link to this manual page? Use this URL:
<https://man.freebsd.org/cgi/man.cgi?query=safe&sektion=4&manpath=FreeBSD+5.2.1-RELEASE>

home | help