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