Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #27
Difficulty: Medium
Linux was the first fully supported 64-bit operating system for consumers.
True or False?
Linux & Unix Commands - Search Man Pages

padlock(4) [freebsd man page]

PADLOCK(4)						   BSD Kernel Interfaces Manual 						PADLOCK(4)

NAME
padlock -- driver for the cryptographic functions and RNG in VIA C3, C7 and Eden processors SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device crypto device padlock Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): padlock_load="YES" DESCRIPTION
The C3 and Eden processor series from VIA include hardware acceleration for AES. The C7 series includes hardware acceleration for AES, SHA1, SHA256 and RSA. All of the above processor series include a hardware random number generator. The padlock driver registers itself to accelerate AES operations and, if available, HMAC/SHA1 and HMAC/SHA256 for crypto(4). It also regis- ters itself to accelerate other HMAC algorithms, although there is no hardware acceleration for those algorithms. This is only needed so padlock can work with ipsec(4). The hardware random number generator supplies data for the kernel random(4) subsystem. SEE ALSO
crypt(3), crypto(4), intro(4), ipsec(4), random(4), crypto(9) HISTORY
The padlock driver first appeared in OpenBSD. The first FreeBSD release to include it was FreeBSD 6.0. AUTHORS
The padlock driver with AES encryption support was written by Jason Wright <jason@OpenBSD.org>. It was ported to FreeBSD and then extended to support SHA1 and SHA256 by Pawel Jakub Dawidek <pjd@FreeBSD.org>. This manual page was written by Christian Brueffer <brueffer@FreeBSD.org>. BSD
February 8, 2010 BSD

Check Out this Related Man Page

SAFE(4) 						   BSD Kernel Interfaces Manual 						   SAFE(4)

NAME
safe -- SafeNet crypto accelerator SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device crypto device cryptodev device safe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): safe_load="YES" sysctl hw.safe.debug sysctl hw.safe.dump sysctl hw.safe.rnginterval sysctl hw.safe.rngbufsize sysctl hw.safe.rngmaxalarm DESCRIPTION
The safe driver supports cards containing SafeNet crypto accelerator chips. 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 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(8) settings control this procedure: hw.safe.rnginterval specifies the time, in sec- onds, between 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 resetting the oscillators. When the driver is compiled with SAFE_DEBUG defined, two sysctl(8) 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 vari- able 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 interrupt registers. HARDWARE
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, public key opera- tions, and full IPsec packet processing. SafeNet 1741 A faster version of the 1141. SEE ALSO
crypt(3), crypto(4), intro(4), ipsec(4), random(4), crypto(9) BUGS
Public key support is not implemented. BSD
April 1, 2006 BSD

Featured Tech Videos