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