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