Annotation of www/crypto.html, Revision 1.138
1.114 jufi 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1 deraadt 2: <html>
3: <head>
1.114 jufi 4: <link rev="made" href="mailto:www@openbsd.org">
5: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
1.1 deraadt 6: <meta name="resource-type" content="document">
1.10 deraadt 7: <meta name="description" content="OpenBSD cryptography">
1.48 beck 8: <meta name="keywords" content="openbsd,cryptography,openssh,openssl,kerberos">
1.112 jason 9: <meta name="keywords" content="ipsec,isakmp,ike,blowfish,des,rsa,dsa">
1.1 deraadt 10: <meta name="distribution" content="global">
1.130 deraadt 11: <meta name="copyright" content="This document copyright 1997-2006 by OpenBSD.">
1.114 jufi 12: <title>Cryptography in OpenBSD</title>
1.1 deraadt 13: </head>
14:
1.114 jufi 15: <body bgcolor="#ffffff" text="#000000" link="#23238e">
1.138 ! jcs 16: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
! 17: <p>
! 18: <h2><font color="#e00000">Cryptography</font></h2>
! 19: <hr>
! 20:
1.128 david 21: <img align="left" alt="[OpenBSD]" height="166" width="197" src="images/blowfish-notext.jpg">
1.45 deraadt 22: <br>
23: <br>
24: <br>
1.61 deraadt 25: "The mantra of any good security engineer is: "Security is not a
1.45 deraadt 26: product, but a process." It's more than designing strong cryptography
27: into a system; it's designing the entire system such that all security
28: measures, including cryptography, work together."<br>
29: <br>
30: -- Bruce Schneier, author of "Applied Cryptography".
1.114 jufi 31: <br clear="all">
32: <hr>
1.32 deraadt 33:
34: <strong>Index</strong><br>
1.128 david 35: <a href="#why">Why do we ship cryptography?</a>.<br>
36: <a href="#ssh">OpenSSH</a>.<br>
1.114 jufi 37: <a href="#prng">Pseudo Random Number Generators</a> (PRNG): ARC4, ...<br>
38: <a href="#hash">Cryptographic Hash Functions</a>: MD5, SHA1, ...<br>
39: <a href="#trans">Cryptographic Transforms</a>: DES, Blowfish, ...<br>
40: <a href="#hardware">Cryptographic Hardware support</a><br>
41: <a href="#people">International Cryptographers wanted</a><br>
42: <a href="#papers">Further Reading</a><br>
1.1 deraadt 43: <p>
1.32 deraadt 44: <hr>
45:
1.114 jufi 46: <a name="why"></a>
47: <h3><font color="#e00000">Why do we ship cryptography?</font></h3><p>
1.32 deraadt 48:
49: In three words: <strong>because we can</strong>.<p>
50:
1.1 deraadt 51: The OpenBSD project is based in Canada.<p>
52:
1.114 jufi 53: The <a href="ECL.html">Export Control List of Canada</a>
1.23 deraadt 54: places no significant restriction on the export of
1.5 deraadt 55: cryptographic software, and is even more explicit about the free
56: export of freely-available cryptographic software. Marc Plumb has
57: done
1.116 nick 58: <a href="http://www.efc.ca/pages/doc/crypto-export.html">
1.31 aaron 59: some research to test the cryptographic laws</a>.
1.2 deraadt 60: <p>
1.1 deraadt 61:
1.3 deraadt 62: Hence the OpenBSD project has embedded cryptography into numerous places
63: in the operating system. We require that the cryptographic software we
1.114 jufi 64: use be <a href="policy.html">freely available and with good licenses</a>.
1.32 deraadt 65: We do not directly use cryptography with nasty patents.
1.13 deraadt 66: We also require that such software is from countries with useful export
1.16 deraadt 67: licenses because we do not wish to break the laws of any country.
68: The cryptographic software components which we use currently were
69: written in Argentina, Australia, Canada, Germany, Greece, Norway, and
70: Sweden.
71: <p>
1.7 deraadt 72:
1.15 deraadt 73: When we create OpenBSD releases or snapshots we build our release
74: binaries in free countries to assure that the sources and binaries we
75: provide to users are free of tainting. In the past our release binary
76: builds have been done in Canada, Sweden, and Germany.<p>
77:
1.124 jmc 78: OpenBSD ships with Kerberos V included. The codebase we use is the
79: exportable Heimdal release from Sweden. Our X11 source has been
80: extended to make use of Kerberos as well.<p>
1.16 deraadt 81:
1.67 deraadt 82:
1.114 jufi 83: <img align="right" src="images/vpnc-test-partner.gif" alt="VPNC TEST PARTNER">
1.87 brad 84: OpenBSD was the first operating system to ship with an IPsec stack.
1.102 brad 85: We've been including IPsec since the OpenBSD 2.1 release in 1997.
1.87 brad 86: Our fully conformant in-kernel IPsec stack, with hardware acceleration
1.66 deraadt 87: based on a number of cards, and our own free ISAKMP daemon, is used as
1.87 brad 88: one of the machines in the IPsec conformance testbed run by
1.67 deraadt 89: <a href="http://www.vpnc.org">VPNC</a>.
1.114 jufi 90: <br clear="all">
1.66 deraadt 91: <p>
92:
1.15 deraadt 93: Today cryptography is an important means for enhancing the <a
1.114 jufi 94: href="security.html">security</a> of an operating system. The
1.42 deraadt 95: cryptography utilized in OpenBSD can be classified into various
96: aspects, described as follows.<p>
1.10 deraadt 97:
1.114 jufi 98: <a name="ssh"></a>
99: <h3><font color="#e00000">OpenSSH</font></h3><p>
1.39 louis 100:
1.55 deraadt 101: As of the 2.6 release, OpenBSD contains
1.50 provos 102: <a href="http://www.openssh.com/">OpenSSH</a>, an absolutely free and
1.128 david 103: patent unencumbered version of ssh.
1.55 deraadt 104: <a href="http://www.openssh.com/">OpenSSH</a> interoperated with ssh
105: version 1 and had many added features,
1.47 provos 106: <ul>
107: <li>
1.88 brad 108: all components of a restrictive nature (i.e., patents, see
1.114 jufi 109: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ssl&sektion=8">ssl(8)</a>)
1.55 deraadt 110: had been directly removed from the source code; any licensed or
111: patented components used external libraries.
1.47 provos 112: <li>
1.55 deraadt 113: had been updated to support ssh protocol 1.5.
1.47 provos 114: <li>
1.124 jmc 115: contained added support for Kerberos authentication and ticket passing.
1.47 provos 116: <li>
1.55 deraadt 117: supported one-time password authentication with
1.114 jufi 118: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=skey&sektion=1">skey(1)</a>.
1.47 provos 119: </ul>
120: <p>
121:
1.93 deraadt 122: Roughly said, we took a free license release of ssh, OpenBSD-ifyed it.
123: About a year later, we extended OpenSSH to also do SSH 2 protocol, the
124: result being support for all 3 major SSH protocols: 1.3, 1.5, 2.0.
1.39 louis 125:
1.114 jufi 126: <a name="prng"></a>
127: <h3><font color="#e00000">Pseudo Random Number Generators</font></h3><p>
1.32 deraadt 128:
1.128 david 129: A Pseudo Random Number Generator (PRNG) provides applications with a stream of
1.10 deraadt 130: numbers which have certain important properties for system security:<p>
131:
132: <ul>
1.11 deraadt 133: <li>It should be impossible for an outsider to predict the output of the
134: random number generator even with knowledge of previous output.
135: <li>The generated numbers should not have repeating patterns which means
136: the PRNG should have a very long cycle length.
1.10 deraadt 137: </ul>
1.32 deraadt 138: <p>
1.10 deraadt 139:
1.13 deraadt 140: A PRNG is normally just an algorithm where the same initial starting
141: values will yield the same sequence of outputs. On a multiuser
142: operating system there are many sources which allow seeding the PRNG
143: with random data. The OpenBSD kernel uses the mouse interrupt timing,
144: network data interrupt latency, inter-keypress timing and disk IO
145: information to fill an entropy pool. Random numbers are available for
146: kernel routines and are exported via devices to userland programs.
1.36 deraadt 147: So far random numbers are used in the following places:<p>
1.13 deraadt 148:
1.10 deraadt 149: <ul>
1.14 deraadt 150: <li>Dynamic sin_port allocation in bind(2).
151: <li>PIDs of processes.
1.26 aaron 152: <li>IP datagram IDs.
1.14 deraadt 153: <li>RPC transaction IDs (XID).
154: <li>NFS RPC transaction IDs (XID).
155: <li>DNS Query-IDs.
156: <li>Inode generation numbers, see getfh(2) and fsirand(8).
1.31 aaron 157: <li>Timing perturbance in traceroute(8).
1.14 deraadt 158: <li>Stronger temporary names for mktemp(3) and mkstemp(3)
159: <li>Randomness added to the TCP ISS value for protection against
160: spoofing attacks.
1.87 brad 161: <li>random padding in IPsec esp_old packets.
1.14 deraadt 162: <li>To generate salts for the various password algorithms.
163: <li>For generating fake S/Key challenges.
1.114 jufi 164: <li>In <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd&sektion=8">isakmpd(8)</a>
1.28 angelos 165: to provide liveness proof of key exchanges.
1.10 deraadt 166: </ul>
1.1 deraadt 167:
1.10 deraadt 168: <p>
1.114 jufi 169: <a name="hash"></a>
170: <h3><font color="#e00000">Cryptographic Hash Functions</font></h3><p>
1.32 deraadt 171:
1.10 deraadt 172: A Hash Function compresses its input data to a string of
1.36 deraadt 173: constant size. For a Cryptographic Hash Function it is infeasible to find:
174:
1.1 deraadt 175: <ul>
1.11 deraadt 176: <li>two inputs which have the same output (collision resistant),
177: <li>a different input for a given input with the same output
178: (2nd preimage resistant).
1.1 deraadt 179: </ul>
1.32 deraadt 180: <p>
1.10 deraadt 181:
1.12 millert 182: In OpenBSD MD5, SHA1, and RIPEMD-160 are used as Cryptographic Hash Functions,
1.36 deraadt 183: e.g:<p>
1.128 david 184: <ul>
1.114 jufi 185: <li>In <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=skey&sektion=1">S/Key(1)</a>
1.27 deraadt 186: to provide one time passwords.
1.114 jufi 187: <li>In <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipsec&sektion=4">IPsec(4)</a>
1.27 deraadt 188: and
1.114 jufi 189: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd&sektion=8">isakmpd(8)</a>
1.27 deraadt 190: to authenticate the data origin of packets and to ensure packet integrity.
191: <li>For FreeBSD-style MD5 passwords (not enabled by default), see
1.136 sthen 192: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=login.conf&sektion=5">
193: login.conf(5)</a>
1.24 niklas 194: <li>In libssl for digital signing of messages.
1.10 deraadt 195: </ul>
1.32 deraadt 196: <p>
1.10 deraadt 197:
1.6 deraadt 198: <p>
1.71 jufi 199: <a name="trans"></a>
1.114 jufi 200: <h3><font color="#e00000">Cryptographic Transforms</font></h3><p>
1.32 deraadt 201:
1.11 deraadt 202: Cryptographic Transforms are used to encrypt and decrypt data. These
203: are normally used with an encryption key for data encryption and with
204: a decryption key for data decryption. The security of a Cryptographic
205: Transform should rely only on the keying material.<p>
1.6 deraadt 206:
1.24 niklas 207: OpenBSD provides transforms like DES, 3DES, Blowfish and Cast for the
1.36 deraadt 208: kernel and userland programs, which are used in many places like:<p>
1.10 deraadt 209: <ul>
1.27 deraadt 210: <li>In libc for creating
1.114 jufi 211: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=blf_key&sektion=3">Blowfish</a>
1.71 jufi 212: passwords. See also the <a href="papers/bcrypt-paper.ps">USENIX paper</a>
1.33 deraadt 213: on this topic.
1.27 deraadt 214: <li>In
1.114 jufi 215: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipsec&sektion=4">IPsec(4)</a>
1.27 deraadt 216: to provide confidentiality for the network layer.
1.114 jufi 217: <li>In <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd&sektion=8">isakmpd(8)</a>
1.87 brad 218: to protect the exchanges where IPsec key material is negotiated.
1.24 niklas 219: <li>In libssl to let applications communicate over the de-facto standard
220: cryptographically secure SSL protocol.
1.10 deraadt 221: </ul>
1.1 deraadt 222:
1.10 deraadt 223: <p>
1.114 jufi 224: <a name="hardware"></a>
225: <h3><font color="#e00000">Cryptographic Hardware Support</font></h3><p>
1.51 deraadt 226:
1.58 louis 227: OpenBSD, starting with 2.7, has begun supporting some cryptography hardware
228: such as accelerators and random number generators.
1.51 deraadt 229: <ul>
1.114 jufi 230: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=crypto&sektion=9">
1.92 jason 231: IPsec crypto dequeue</a></b><br>
1.87 brad 232: Our IPsec stack has been modified so that cryptographic functions get
233: done out-of-line. Most simple software IPsec stacks need to do
1.82 pvalchev 234: cryptography when processing each packet. This results in synchronous
1.73 aaron 235: performance. To use hardware properly and speedily one needs to separate
1.51 deraadt 236: these two components, as we have done. Actually, doing this gains some
237: performance even for the software case.
238: <p>
1.114 jufi 239: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=hifn&sektion=4">
1.88 brad 240: Hifn 7751</a></b><br>
241: Cards using the Hifn 7751 can be used as a symmetric cryptographic
1.101 deraadt 242: accelerator, i.e., the
243: <a href="http://www.soekris.com/vpn1201.htm">Soekris VPN1201 or VPN1211</a>
244: (<a href="http://www.soekris.com/how_to_buy.htm">to buy</a>)
245: or
246: <a href="http://www.powercrypt.com">PowerCrypt</a>.
1.51 deraadt 247: Current performance using a single Hifn 7751 on each end of a tunnel
1.88 brad 248: is 64Mbit/sec for 3DES/SHA1 ESP, nearly a 600% improvement over
249: using a P3/550 CPU. Further improvements are under way to resolve a
1.51 deraadt 250: few more issues, but as of April 13, 2000 the code is considered
1.53 deraadt 251: stable. We wrote our own driver for supporting this chip, rather
252: than using the (USA-written)
1.88 brad 253: <a href="http://www.powercrypt.com">PowerCrypt</a> driver, as well
1.87 brad 254: our driver links in properly to the IPsec stack.
1.53 deraadt 255: The 7751 is now considered slow by industry standards and many vendors
1.88 brad 256: have faster chips (even Hifn now has a faster but more expensive
1.89 jufi 257: chip). Peak performance with 3DES SHA1 ESP is around 64Mbit/sec.
1.60 deraadt 258: <p>
1.97 jason 259: After 2.9 shipped, support was added for the Hifn 7951 chip, a
260: simplified version of the 7751 which adds a public key accelerator
261: (unsupported) and a random number generator (supported). Cards
262: were donated by <a href="http://www.soekris.com/">Soekris Engineering</a>.
263: <p>
264: After 3.0 shipped, support was added for the Hifn 7811 chip, a
265: faster version of the 7751 (around 130Mbit/s) with a random number
266: generator. A card was donated by <a href="http://www.gtgi.com/">GTGI</a>.
267: <p>
1.118 jason 268: After 3.2 shipped, support was added for the LZS compression algorithm
269: used by <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipcomp&sektion=4">ipcomp(4)</a>.
270: <p>
1.123 jason 271: After 3.4 shipped, support was added for the 7955 and 7956 chips.
272: In addition to all the features of the previous 7951 chip, these add AES.
273: <p>
1.118 jason 274: Hifn was initially a difficult company to deal with (threatening to sue
1.119 deraadt 275: us over our non-USA reverse engineering of their crypto unlock algorithm),
276: but more recently they have been very helpful in providing boards and
277: support.
1.53 deraadt 278: <p>
1.69 deraadt 279:
1.114 jufi 280: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=lofn&sektion=4">
1.92 jason 281: Hifn 6500</a></b><br>
1.86 brad 282: This device is an asymmetric crypto unit. It has support for RSA, DSA,
1.69 deraadt 283: and DH algorithms, as well as other major big number functions. It also
284: contains a very high performance random number generator. We have one
1.107 deraadt 285: device, full documentation, and sample code. As of OpenBSD 3.1,
1.105 jason 286: both the random number generator and big number unit are working.
287: <p>
288:
1.114 jufi 289: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=nofn&sektion=4">
1.105 jason 290: Hifn 7814/7851/7854</a></b><br>
291: This device is a packet processor and asymmetric crypto unit. It has
292: support for RSA, DSA, and DH algorithms, as well as other major big number
293: functions and also has a random number generator. Currently, only the
294: big number engine and the random number generator are supported (no
295: packet transforms).
1.69 deraadt 296: <p>
297:
1.114 jufi 298: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ubsec&sektion=4">
1.134 reyk 299: Broadcom BCM5801/BCM5802/BCM5805/BCM5820/BCM5821/BCM5822/5823/5825/5860/5861/5862
1.105 jason 300: (or beta chip Bluesteelnet 5501/5601)</a></b><br>
1.65 deraadt 301: Just after the OpenBSD 2.7 release, we succeeded at adding preliminary
302: support for these early release parts provided to us by the vendor,
1.76 deraadt 303: specifically starting with the test chip 5501.
1.69 deraadt 304: These devices provide the highest performance symmetric cryptography
305: we have seen.
306: <p>
1.59 deraadt 307: Bluesteelnet was bought by Broadcom and started making real parts.
1.84 pvalchev 308: Their new BCM5805 is similar, except that they also add an asymmetric
1.65 deraadt 309: engine for running DSA, RSA, and other such algorithms. With approximate
1.88 brad 310: performance starting at more than four times as fast as the Hifn,
1.65 deraadt 311: hopefully this chip will become more common soon.
1.60 deraadt 312: <p>
313: The Broadcom/Bluesteelnet people have been great to deal with. They gave
1.69 deraadt 314: us complete documentation and sample code for their chips and a
315: sufficient number of cards to test with.
1.60 deraadt 316: <p>
1.74 deraadt 317: Post 2.8, this driver was also modified to generate random numbers on
318: the BCM5805 and similar versions, and feed that data into the kernel
319: entropy pool.
320: <p>
1.96 jason 321: Post 2.9, support was added for the BCM5820, which is mostly just a
322: faster (64bit, higher clock speed) version of the BCM5805. Untested
323: support for the BCM5821 was also added post 3.0.
1.100 jason 324: <p>
1.111 jufi 325: As of 3.1, the big num engine is supported, and RSA/DH/DSA operations
1.107 deraadt 326: can be accelerated.
327: <p>
1.108 jason 328: Support for the BCM5801, BCM5802, BCM5821 and BCM5822 was added before
1.109 jason 329: OpenBSD 3.2 (the untested BCM5821 support in 3.1 was broken because of
330: some undocumented interrupt handling requirements).
1.108 jason 331: <p>
1.134 reyk 332: Partial support for BCM5823 was added for 3.4.
333: <p>
334: Support for the BCM5825, BCM5860, BCM5861, and BCM5862 including support
1.135 jsg 335: for AES with the BCM5823 or newer was added after 4.5.
1.122 jason 336: <p>
1.60 deraadt 337:
1.114 jufi 338: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ises&sektion=4">
1.88 brad 339: Securealink PCC-ISES</a></b><br>
1.115 jufi 340: The <a href="http://www.safenet-inc.com/technology/chips/safexcel_ises.asp">
1.128 david 341: PCC-ISES</a> is a new chipset from the Netherlands. We have received
342: sample hardware and documentation, and work on a driver is in progress.
343: At the moment, the driver is capable of feeding random numbers into
1.115 jufi 344: the kernel entropy pool.
1.60 deraadt 345: <p>
1.130 deraadt 346:
347: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=safe&sektion=4">
1.131 deraadt 348: SafeNet SafeXcel 1141/1741</a></b><br>
1.130 deraadt 349: After 3.4 shipped, support was for added for these two chips (found on various
350: <a href="http://www.safenet-inc.com/products/accCards/">SafeNet</a>
351: crypto cards. Supports DES, Triple-DES, AES, MD5, and SHA-1 symmetric crypto
352: operations, RNG, public key operations, and full IPsec packet processing.
353: <p>
354:
355: <li><b>SafeNet SafeXcel 1840</b><br>
356: We have received documentation and sample hardware for the
357: <a href="http://www.safenet-inc.com/products/chips/safeXcel1840.asp">SafeNet 1840</a>
358: crypto chip. Work to support at least the RNG and symmetric cryptography of
359: these devices has started.
360: <p>
361:
1.88 brad 362: <li><b>SafeNet SafeXcel 2141</b><br>
1.60 deraadt 363: We have received documentation and sample hardware for the
1.130 deraadt 364: <a href="http://www.safenet-inc.com/products/chips/safeXcel2141.asp">SafeNet 2141</a>
365: crypto chip. Work to support at least the symmetric cryptography of
1.72 deraadt 366: these devices has started.
1.57 deraadt 367: <p>
1.130 deraadt 368:
1.114 jufi 369: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=txp&sektion=4">
1.110 jason 370: 3com 3cr990</a></b><br>
1.77 deraadt 371: 3com gave us a driver to support the ethernet component of this chipset,
1.79 ericj 372: and based on that, we have written our own ethernet driver. This driver
373: has now been integrated once we were able to get a free license on the
1.110 jason 374: microcode. Due to poor documentation and lack of cooperation (partly
375: because of the high turnover rates at 3Com), the IPsec functions of the
376: chip are not supported.... so this turned out to be a less than completely
377: useful exercise.
1.69 deraadt 378: <p>
379:
1.87 brad 380: <li><b>Intel IPsec card</b><br>
1.77 deraadt 381: Much like Intel does for all their networking division components, and
1.93 deraadt 382: completely unlike most other vendors, Intel steadfastly refuses to provide
1.77 deraadt 383: us with documentation. We have talked to about five technical people who
384: are involved in the development of those products. They all want us to
385: have documentation. They commend us on what we have done. But their hands
386: are tied by management who does not perceive a benefit to themselves for
387: providing documentation. Forget about Intel. (If you want to buy gigabit
388: ethernet hardware, we recommend anything else... for the same reason:
389: most drivers we have for Intel networking hardware were written without
390: documentation).
1.52 deraadt 391: <p>
1.69 deraadt 392:
1.114 jufi 393: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pchb&sektion=4">
1.80 deraadt 394: Intel 82802AB/82802AC Firmware Hub RNG</a></b><br>
1.74 deraadt 395: The 82802 FWH chip (found on i810, i820, i840, i850, and i860 motherboards)
1.87 brad 396: contains a random number generator (RNG). High-performance IPsec
1.74 deraadt 397: requires more random number entropy. As of April 10, 2000, we support
1.90 jsyn 398: the RNG. We will add support for other RNGs found on crypto chips.
1.69 deraadt 399: <p>
400:
1.120 deraadt 401: <li><b>VIA C3 RNG</b><br>
1.129 david 402: The newer VIA C3 CPU contains a random number generator as an instruction.
1.120 deraadt 403: As of <a href="33.html">3.3</a> this random number generator is used
404: inside the kernel to feed the entropy pool.
405: <p>
406:
1.127 deraadt 407: <li><b>VIA C3 AES instructions</b><br>
1.129 david 408: VIA C3 CPUs with a step 8 or later Nehemiah core contains an AES
1.127 deraadt 409: implementation accessible via simple instructions. As of <a
410: href="34.html">3.4</a> the kernel supports them to be used in an
411: IPsec context and exported by <tt>/dev/crypto</tt>. As of <a
412: href="35.html">3.5</a> performances have been greatly improved
413: and OpenSSL now uses the new instruction directly when available
414: without the need to enter the kernel, resulting in vastly
415: improved speed (AES-128 measured at 780MByte/sec) for applications
416: using OpenSSL to perform AES encryption.
417: <p>
418:
1.52 deraadt 419: <li><b>OpenSSL</b><br>
1.107 deraadt 420: Years ago, we had a grand scheme to support crypto cards that can do
421: RSA/DH/DSA automatically via OpenSSL calls. As of OpenBSD 3.2, that
422: support works, and any card that is supported with such functionality
423: will automatically use the hardware, including OpenSSH and httpd in
424: SSL mode. No application changes are required.
1.51 deraadt 425: </ul>
426:
427: <p>
1.69 deraadt 428: <b>If people wish to help with writing drivers,
1.114 jufi 429: <a href="#people">come and help us</a>.</b>
1.69 deraadt 430:
431: <p>
1.114 jufi 432: <a name="people"></a>
433: <h3><font color="#e00000">International Cryptographers Wanted</font></h3><p>
1.32 deraadt 434:
435: Of course, our project needs people to work on these systems. If any
436: non-American cryptographer who meets the constraints listed earlier is
437: interested in helping out with embedded cryptography in OpenBSD,
438: please contact us.<p>
439:
1.33 deraadt 440: <p>
1.114 jufi 441: <a name="papers"></a>
442: <h3><font color="#e00000">Further Reading</font></h3><p>
1.33 deraadt 443:
444: A number of papers have been written by OpenBSD team members, about
445: cryptographic changes they have done in OpenBSD. The postscript
1.34 deraadt 446: versions of these documents are available as follows.<p>
1.33 deraadt 447:
448: <ul>
1.43 deraadt 449: <li>A Future-Adaptable Password Scheme.<br>
1.114 jufi 450: <a href="events.html#usenix99">Usenix 1999</a>,
451: by <a href="mailto:provos@openbsd.org">Niels Provos</a>,
452: <a href="mailto:dm@openbsd.org">David Mazieres</a>.<br>
453: <a href="papers/bcrypt-paper.ps">paper</a> and
454: <a href="papers/bcrypt-slides.ps">slides</a>.
1.43 deraadt 455: <p>
456: <li>Cryptography in OpenBSD: An Overview.<br>
1.114 jufi 457: <a href="events.html#usenix99">Usenix 1999</a>,
458: by <a href="mailto:deraadt@openbsd.org">Theo de Raadt</a>,
459: <a href="mailto:niklas@openbsd.org">Niklas Hallqvist</a>,
460: <a href="mailto:art@openbsd.org">Artur Grabowski</a>,
461: <a href="mailto:angelos@openbsd.org">Angelos D. Keromytis</a>,
462: <a href="mailto:provos@openbsd.org">Niels Provos</a>.<br>
463: <a href="papers/crypt-paper.ps">paper</a> and
464: <a href="papers/crypt-slides.ps">slides</a>.
1.62 niklas 465: <p>
466: <li>Implementing Internet Key Exchange (IKE).<br>
1.114 jufi 467: <a href="events.html#usenix2000">Usenix 2000</a>,
468: by <a href="mailto:niklas@openbsd.org">Niklas Hallqvist</a> and
469: <a href="mailto:angelos@openbsd.org">Angelos D. Keromytis</a>.<br>
470: <a href="papers/ikepaper.ps">paper</a> and
471: <a href="papers/ikeslides.ps">slides</a>.
472: <p>
473: <li>Encrypting Virtual Memory.<br>
474: <a href="events.html#sec2000">Usenix Security 2000</a>,
475: <a href="mailto:provos@openbsd.org">Niels Provos</a>.<br>
1.128 david 476: <a href="papers/swapencrypt.ps">paper</a> and
1.114 jufi 477: <a href="papers/swapencrypt-slides.ps">slides</a>.
1.121 jason 478: <p>
479: <li>The Design of the OpenBSD Cryptographic Framework.<br>
480: <a href="events.html#usenix2003">Usenix 2003</a>, by
481: <a href="mailto:angelos@openbsd.org">Angelos D. Keromytis</a>,
482: <a href="mailto:jason@openbsd.org">Jason L. Wright</a>, and
483: <a href="mailto:deraadt@openbsd.org">Theo de Raadt</a>.<br>
484: <a href="papers/ocf.pdf">paper</a>.
1.133 steven 485: <p>
1.132 jason 486: <li>Cryptography As an Operating System Service: A Case Study.<br>
1.133 steven 487: <a href="http://www.acm.org/tocs/">ACM Transactions on Computer Systems</a>,
1.132 jason 488: February 2006, by
489: <a href="mailto:angelos@openbsd.org">Angelos D. Keromytis</a>,
490: <a href="mailto:jason@openbsd.org">Jason L. Wright</a>, and
491: <a href="mailto:deraadt@openbsd.org">Theo de Raadt</a>.<br>
492: <a href="papers/crypt-service.pdf">paper</a>.
1.33 deraadt 493: </ul>
494:
1.32 deraadt 495: <p>
1.1 deraadt 496: <hr>
1.114 jufi 497: <a href="index.html"><img height="24" width="24" src="back.gif" border="0" alt="OpenBSD"></a>
498: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.10 deraadt 499: <br>
1.138 ! jcs 500: <small>$OpenBSD: crypto.html,v 1.137 2013/03/25 17:37:43 deraadt Exp $</small>
1.1 deraadt 501:
1.10 deraadt 502: </body>
503: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to crypto.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www