xref: /netbsd-src/share/man/man4/hifn.4 (revision 9c94f9d81663a473c3bbee8017e74deee019451a)
1.\"	$NetBSD: hifn.4,v 1.10 2020/05/17 01:00:34 riastradh Exp $
2.\"	$OpenBSD: hifn.4,v 1.32 2002/09/26 07:55:40 miod Exp $
3.\"	$FreeBSD: src/share/man/man4/hifn.4,v 1.1.2.2 2003/10/08 23:57:50 sam Exp $
4.\"
5.\" Copyright (c) 2000 Theo de Raadt
6.\" All rights reserved.
7.\"
8.\" Redistribution and use in source and binary forms, with or without
9.\" modification, are permitted provided that the following conditions
10.\" are met:
11.\" 1. Redistributions of source code must retain the above copyright
12.\"    notice, this list of conditions and the following disclaimer.
13.\" 2. Redistributions in binary form must reproduce the above copyright
14.\"    notice, this list of conditions and the following disclaimer in the
15.\"    documentation and/or other materials provided with the distribution.
16.\" 3. The name of the author may not be used to endorse or promote products
17.\"    derived from this software without specific prior written permission.
18.\"
19.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
20.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
21.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
22.\" DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
23.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
24.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
25.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
27.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
28.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
29.\" POSSIBILITY OF SUCH DAMAGE.
30.\"
31.Dd June 13, 2018
32.Dt HIFN 4
33.Os
34.Sh NAME
35.Nm hifn
36.Nd Hifn 7751/7951/7811/7955/7956 crypto accelerator
37.Sh SYNOPSIS
38.Cd "hifn* at pci? dev ? function ?"
39.Sh DESCRIPTION
40The
41.Nm
42driver supports various cards containing the Hifn 7751, 7951,
437811, 7955, and 7956
44chipsets, such as
45.Bl -tag -width namenamenamena -offset indent
46.It Invertex AEON
47No longer being made.
48Came as 128KB SRAM model, or 2MB DRAM model.
49.It Hifn 7751
50Reference board with 512KB SRAM.
51.It PowerCrypt
52Comes with 512KB SRAM.
53.It XL-Crypt
54Only board based on 7811 (which is faster than 7751 and has
55a random number generator).
56.It NetSec 7751
57Supports the most IPsec sessions, with 1MB SRAM.
58.It Soekris Engineering vpn1201 and vpn1211
59Contains a 7951 and supports symmetric and random number operations.
60.It Soekris Engineering vpn1401 and vpn1411
61Contains a 7955 and supports symmetric and random number operations.
62.El
63.Pp
64The
65.Nm
66driver registers itself to accelerate DES, Triple-DES,
67AES (7955 and 7956 only), ARC4, MD5,
68MD5-HMAC, SHA1, and SHA1-HMAC operations for
69.Xr opencrypto 9 ,
70and thus for
71.Xr ipsec 4
72and
73.Xr crypto 4 .
74.Pp
75The Hifn
76.Tn 7951 ,
77.Tn 7811 ,
78.Tn 7955 ,
79and
80.Tn 7956
81may also supply data to the kernel
82.Xr rnd 4
83subsystem.
84.Sh SEE ALSO
85.Xr crypto 4 ,
86.Xr intro 4 ,
87.Xr ipsec 4 ,
88.Xr rnd 4 ,
89.Xr opencrypto 9
90.Sh HISTORY
91The
92.Nm
93device driver appeared in
94.Ox 2.7 .
95The
96.Nm
97device driver was imported to
98.Fx 5.0 ,
99back-ported to
100.Fx 4.8 ,
101and subsequently imported into
102.Nx 2.0 .
103.Sh CAVEATS
104The Hifn 9751 shares the same PCI ID.
105This chip is basically a 7751, but with the cryptographic functions missing.
106Instead, the 9751 is only capable of doing compression.
107Since we do not currently attempt to use any of these chips to do
108compression, the 9751-based cards are not useful.
109.Pp
110Support for the 7955 and 7956 is incomplete; the asymmetric crypto
111facilities are to be added and the performance is suboptimal.
112.Sh BUGS
113The 7751 chip starts out at initialization by only supporting compression.
114A proprietary algorithm, which has been reverse engineered, is required to
115unlock the cryptographic functionality of the chip.
116It is possible for vendors to make boards which have a lock ID not known
117to the driver, but all vendors currently just use the obvious ID which is
11813 bytes of 0.
119