Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ubsec(4) [netbsd man page]

UBSEC(4)						   BSD Kernel Interfaces Manual 						  UBSEC(4)

NAME
ubsec -- Broadcom and BlueSteel uBsec 5x0x crypto accelerator SYNOPSIS
ubsec* at pci? dev ? function ? DESCRIPTION
The ubsec driver supports cards containing any of the following chips: Bluesteel 5501 The original chipset, no longer made. This extremely rare unit was not very fast, lacked an RNG, and had a number of other bugs. Bluesteel 5601 A faster and fixed version of the original, with a random number unit and large number engine added. Broadcom BCM5801 A BCM5805 without public key engine or random number generator. Broadcom BCM5802 A slower version of the BCM5805. Broadcom BCM5805 Faster version of Bluesteel 5601. Broadcom BCM5820 64 bit version of the chip, and significantly more advanced. Broadcom BCM5821 Faster version of the BCM5820. (This is the chip found on the Sun Crypto Accelerator 1000.) Broadcom BCM5822 Faster version of the BCM5820. Broadcom BCM5823 Faster version of the BCM5822. Broadcom BCM5823 Faster version of the BCM5821, with AES hardware. The ubsec driver registers itself to accelerate DES, Triple-DES, MD5, SHA1, MD5-HMAC, and SHA1-HMAC operations for opencrypto(9), and thus for fast_ipsec(4) and crypto(4). On those models which contain a public key engine (almost all of the more recent ones), this feature is registered with the crypto(4) subsys- tem. On all models except the Bluesteel 5501 and Broadcom 5801, the driver registers itself to provide random data to the rnd(4) subsystem. SEE ALSO
crypto(4), fast_ipsec(4), intro(4), rnd(4), opencrypto(9) HISTORY
The ubsec device driver appeared in OpenBSD 2.8. The ubsec device driver was imported to FreeBSD 5.0, back-ported to FreeBSD 4.8, and subse- quently imported to NetBSD 2.0. BUGS
The BCM5801 and BCM5802 have not actually been tested. Whilst some of the newer chips support AES, AES is not supported by the driver. BSD
June 10, 2000 BSD

Check Out this Related Man Page

HIFN(4) 						   BSD Kernel Interfaces Manual 						   HIFN(4)

NAME
hifn -- Hifn 7751/7951/7811/7955/7956 crypto accelerator SYNOPSIS
hifn* at pci? dev ? function ? DESCRIPTION
The hifn driver supports various cards containing the Hifn 7751, 7951, 7811, 7955, and 7956 chipsets, such as Invertex AEON No longer being made. Came as 128KB SRAM model, or 2MB DRAM model. Hifn 7751 Reference board with 512KB SRAM. PowerCrypt See http://www.powercrypt.com/. Comes with 512KB SRAM. XL-Crypt See http://www.powercrypt.com/. Only board based on 7811 (which is faster than 7751 and has a random number genera- tor). NetSec 7751 See http://www.netsec.net/. Supports the most IPsec sessions, with 1MB SRAM. Soekris Engineering vpn1201 and vpn1211 See http://www.soekris.com/. Contains a 7951 and supports symmetric and random number operations. Soekris Engineering vpn1401 and vpn1411 See http://www.soekris.com/. Contains a 7955 and supports symmetric and random number operations. The hifn driver registers itself to accelerate DES, Triple-DES, AES (7955 and 7956 only), ARC4, MD5, MD5-HMAC, SHA1, and SHA1-HMAC operations for opencrypto(9), and thus for fast_ipsec(4) and crypto(4). The Hifn 7951, 7811, 7955, and 7956 may also supply data to the kernel rnd(4) subsystem. SEE ALSO
crypto(4), fast_ipsec(4), intro(4), rnd(4), opencrypto(9) HISTORY
The hifn device driver appeared in OpenBSD 2.7. The hifn device driver was imported to FreeBSD 5.0, back-ported to FreeBSD 4.8, and subse- quently imported into NetBSD 2.0. CAVEATS
The Hifn 9751 shares the same PCI ID. This chip is basically a 7751, but with the cryptographic functions missing. Instead, the 9751 is only capable of doing compression. Since we do not currently attempt to use any of these chips to do compression, the 9751-based cards are not useful. Support for the 7955 and 7956 is incomplete; the asymmetric crypto facilities are to be added and the performance is suboptimal. Supplying data to the kernel rnd(4) subsystem has been disabled, pending verification that the on-chip RNG is statistically adequate. BUGS
The 7751 chip starts out at initialization by only supporting compression. A proprietary algorithm, which has been reverse engineered, is required to unlock the cryptographic functionality of the chip. It is possible for vendors to make boards which have a lock ID not known to the driver, but all vendors currently just use the obvious ID which is 13 bytes of 0. BSD
October 8, 2003 BSD
Man Page