Annotation of www/crypto.html, Revision 1.81
1.10 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict Level 2//EN//2.0">
1.1 deraadt 2: <html>
3: <head>
1.10 deraadt 4: <title>Cryptography in OpenBSD</title>
1.1 deraadt 5: <link rev=made href=mailto:www@openbsd.org>
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">
9: <meta name="keywords" content="ipsec,photuris,isakmp,ike,blowfish,des,rsa,dsa">
1.1 deraadt 10: <meta name="distribution" content="global">
11: <meta name="copyright" content="This document copyright 1997 by OpenBSD.">
12: </head>
13:
14: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
1.45 deraadt 15: <img align=left alt="[OpenBSD]" height=166 width=197 SRC="images/blowfish-notext.jpg">
16: <br>
17: <br>
18: <br>
1.61 deraadt 19: "The mantra of any good security engineer is: "Security is not a
1.45 deraadt 20: product, but a process." It's more than designing strong cryptography
21: into a system; it's designing the entire system such that all security
22: measures, including cryptography, work together."<br>
23: <br>
24: -- Bruce Schneier, author of "Applied Cryptography".
25: <br clear=all>
1.37 deraadt 26: <h2><font color=#e00000>Cryptography</font><hr></h2>
1.32 deraadt 27:
28: <strong>Index</strong><br>
1.41 louis 29: <a href=#why>Why do we ship cryptography?</a>.<br>
1.47 provos 30: <a href=#ssh>OpenSSH</a>.<br>
1.32 deraadt 31: <a href=#prng>Pseudo Random Number Generators</a> (PRNG): ARC4, ...<br>
32: <a href=#hash>Cryptographic Hash Functions</a>: MD5, SHA1, ...<br>
33: <a href=#trans>Cryptographic Transforms</a>: DES, Blowfish, ...<br>
1.51 deraadt 34: <a href=#hardware>Cryptographic Hardware support</a><br>
1.32 deraadt 35: <a href=#people>International Cryptographers wanted</a><br>
1.33 deraadt 36: <a href=#papers>Further Reading</a><br>
1.1 deraadt 37: <p>
1.32 deraadt 38: <hr>
39:
40: <a name=why></a>
1.42 deraadt 41: <h3><font color=#e00000>Why do we ship cryptography?</font></h3><p>
1.32 deraadt 42:
43: In three words: <strong>because we can</strong>.<p>
44:
1.1 deraadt 45: The OpenBSD project is based in Canada.<p>
46:
1.23 deraadt 47: The <a href=ECL.html>Export Control List of Canada</a>
48: places no significant restriction on the export of
1.5 deraadt 49: cryptographic software, and is even more explicit about the free
50: export of freely-available cryptographic software. Marc Plumb has
51: done
1.2 deraadt 52: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>
1.31 aaron 53: some research to test the cryptographic laws</a>.
1.2 deraadt 54: <p>
1.1 deraadt 55:
1.3 deraadt 56: Hence the OpenBSD project has embedded cryptography into numerous places
57: in the operating system. We require that the cryptographic software we
58: use be <a href=policy.html>freely available and with good licenses</a>.
1.32 deraadt 59: We do not directly use cryptography with nasty patents.
1.13 deraadt 60: We also require that such software is from countries with useful export
1.16 deraadt 61: licenses because we do not wish to break the laws of any country.
62: The cryptographic software components which we use currently were
63: written in Argentina, Australia, Canada, Germany, Greece, Norway, and
64: Sweden.
65: <p>
1.7 deraadt 66:
1.15 deraadt 67: When we create OpenBSD releases or snapshots we build our release
68: binaries in free countries to assure that the sources and binaries we
69: provide to users are free of tainting. In the past our release binary
70: builds have been done in Canada, Sweden, and Germany.<p>
71:
1.16 deraadt 72: OpenBSD ships with Kerberos IV included. The codebase we use is the
1.17 deraadt 73: exportable KTH-based release from Sweden. Our X11 source has been
1.81 ! hin 74: extended to make use of Kerberos IV as well.<p>
! 75:
! 76: We are working on integration of the Heimdal implementation of Kerberos V,
! 77: also from the KTH people in Sweden. We hope to be able to ship OpenBSD
! 78: with Kerberos V during 2001.
! 79: <p>
1.16 deraadt 80:
1.67 deraadt 81:
1.66 deraadt 82: <img align=right src="images/vpnc-test-partner.gif">
83: OpenBSD was the first operating system to ship with an IPSEC stack.
84: We've been including IPSEC since early OpenBSD 2.1 release in 1997.
85: Our fully conformant in-kernel IPSEC stack, with hardware acceleration
86: based on a number of cards, and our own free ISAKMP daemon, is used as
1.67 deraadt 87: one of the machines in the IPSEC conformance testbed run by
88: <a href="http://www.vpnc.org">VPNC</a>.
1.66 deraadt 89: <br clear=all>
90: <p>
91:
1.15 deraadt 92: Today cryptography is an important means for enhancing the <a
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.39 louis 97: <a name=ssh></a>
1.47 provos 98: <h3><font color=#e00000>OpenSSH</font></h3><p>
1.39 louis 99:
1.40 deraadt 100: What is the first thing most people do after installing OpenBSD?
1.55 deraadt 101: They install Secure Shell
102: (<a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ssh>ssh</a>)
1.46 deraadt 103: from the ports tree or the packages on the FTP sites. Until now, that is.<p>
1.39 louis 104:
1.55 deraadt 105: As of the 2.6 release, OpenBSD contains
1.50 provos 106: <a href="http://www.openssh.com/">OpenSSH</a>, an absolutely free and
107: patent unencumbered version of ssh.
1.55 deraadt 108: As of the OpenBSD 2.6 release date,
109: <a href="http://www.openssh.com/">OpenSSH</a> interoperated with ssh
110: version 1 and had many added features,
1.47 provos 111: <ul>
112: <li>
113: all components of a restrictive nature (ie. patents, see
114: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ssl>ssl</a>))
1.55 deraadt 115: had been directly removed from the source code; any licensed or
116: patented components used external libraries.
1.47 provos 117: </li>
118: <li>
1.55 deraadt 119: had been updated to support ssh protocol 1.5.
1.47 provos 120: </li>
121: <li>
1.55 deraadt 122: contained added support for
1.47 provos 123: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=kerberos>kerberos</a>
124: authentication and ticket passing.
125: </li>
126: <li>
1.55 deraadt 127: supported one-time password authentication with
1.47 provos 128: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=skey>skey</a>.
129: </li>
130: </ul>
131: <p>
132:
1.55 deraadt 133: Roughly, we took a free license release of ssh and OpenBSD-ifyed it.
134: We get around the USA-based RSA patent by providing an easy way to
1.47 provos 135: automatically download and install a RSA-enabled package containing
136: shared library versions of libcrypto and libssl. These packages are
137: based on OpenSSL. People living outside the USA can freely use the
1.40 deraadt 138: RSA patented code, while people inside the USA can freely use it for
1.47 provos 139: non-commercial purposes. It appears as if companies inside the USA
140: can use the RSA libraries too, as long as RSA is not used in a profit
141: generating role.<p>
1.39 louis 142:
1.55 deraadt 143: But this way almost everyone will get ssh built into their OS.<p>
144:
145: <strong>NEW! OpenSSH supports protocol 2.0!</strong><p>
146:
147: Recently, we have extended OpenSSH so that it also does SSH 2 protocol.
148: Having a ssh daemon which can do all 3 major SSH protocols
149: (1.3, 1.5, 2.0) permits us much flexibility. Protocol 2.0 does not
150: use RSA for it's public key cryptography, relying instead on the DH
151: and DSA algorithms. In OpenBSD 2.7 -- which will ship with the new
152: OpenSSH -- you get protocol 2.0 support right out of the box! If
153: you wish to also support protocol 1.3 and 1.5, you simply add the
154: RSA package (as described our
155: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ssl>ssl</a>
156: manual page), and restart the daemon.
1.39 louis 157:
1.18 deraadt 158: <a name=prng></a>
1.42 deraadt 159: <h3><font color=#e00000>Pseudo Random Number Generators</font></h3><p>
1.32 deraadt 160:
1.10 deraadt 161: A Pseudo Random Number Generator (PRNG) provides applications with a stream of
162: numbers which have certain important properties for system security:<p>
163:
164: <ul>
1.11 deraadt 165: <li>It should be impossible for an outsider to predict the output of the
166: random number generator even with knowledge of previous output.
167: <li>The generated numbers should not have repeating patterns which means
168: the PRNG should have a very long cycle length.
1.10 deraadt 169: </ul>
1.32 deraadt 170: <p>
1.10 deraadt 171:
1.13 deraadt 172: A PRNG is normally just an algorithm where the same initial starting
173: values will yield the same sequence of outputs. On a multiuser
174: operating system there are many sources which allow seeding the PRNG
175: with random data. The OpenBSD kernel uses the mouse interrupt timing,
176: network data interrupt latency, inter-keypress timing and disk IO
177: information to fill an entropy pool. Random numbers are available for
178: kernel routines and are exported via devices to userland programs.
1.36 deraadt 179: So far random numbers are used in the following places:<p>
1.13 deraadt 180:
1.10 deraadt 181: <ul>
1.14 deraadt 182: <li>Dynamic sin_port allocation in bind(2).
183: <li>PIDs of processes.
1.26 aaron 184: <li>IP datagram IDs.
1.14 deraadt 185: <li>RPC transaction IDs (XID).
186: <li>NFS RPC transaction IDs (XID).
187: <li>DNS Query-IDs.
188: <li>Inode generation numbers, see getfh(2) and fsirand(8).
1.31 aaron 189: <li>Timing perturbance in traceroute(8).
1.14 deraadt 190: <li>Stronger temporary names for mktemp(3) and mkstemp(3)
191: <li>Randomness added to the TCP ISS value for protection against
192: spoofing attacks.
1.29 deraadt 193: <li>random padding in IPSEC esp_old packets.
1.14 deraadt 194: <li>To generate salts for the various password algorithms.
195: <li>For generating fake S/Key challenges.
1.44 provos 196: <li>In <a href=http://www.physnet.uni-hamburg.de/provos/photuris/>photurisd</a>
1.28 angelos 197: and <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd>isakmpd</a>
198: to provide liveness proof of key exchanges.
1.10 deraadt 199: </ul>
1.1 deraadt 200:
1.10 deraadt 201: <p>
1.18 deraadt 202: <a name=hash></a>
1.42 deraadt 203: <h3><font color=#e00000>Cryptographic Hash Functions</font></h3><p>
1.32 deraadt 204:
1.10 deraadt 205: A Hash Function compresses its input data to a string of
1.36 deraadt 206: constant size. For a Cryptographic Hash Function it is infeasible to find:
207:
1.1 deraadt 208: <ul>
1.11 deraadt 209: <li>two inputs which have the same output (collision resistant),
210: <li>a different input for a given input with the same output
211: (2nd preimage resistant).
1.1 deraadt 212: </ul>
1.32 deraadt 213: <p>
1.10 deraadt 214:
1.12 millert 215: In OpenBSD MD5, SHA1, and RIPEMD-160 are used as Cryptographic Hash Functions,
1.36 deraadt 216: e.g:<p>
1.10 deraadt 217: <ul>
1.27 deraadt 218: <li>In <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=skey>S/Key</a>
219: to provide one time passwords.
1.78 brad 220: <li>In <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ipsec>IPSEC</a>,
1.44 provos 221: <a href=http://www.physnet.uni-hamburg.de/provos/photuris/>photurisd</a>
1.27 deraadt 222: and
223: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd>isakmpd(8)</a>
224: to authenticate the data origin of packets and to ensure packet integrity.
225: <li>For FreeBSD-style MD5 passwords (not enabled by default), see
226: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=passwd.conf&sektion=5>
227: passwd.conf(5)</a>
228: <li>For TCP SYN cookie support (not enabled by default), see
229: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=options&sektion=4>
230: options(4)</a>
1.24 niklas 231: <li>In libssl for digital signing of messages.
1.10 deraadt 232: </ul>
1.32 deraadt 233: <p>
1.10 deraadt 234:
1.6 deraadt 235: <p>
1.71 jufi 236: <a name="trans"></a>
1.42 deraadt 237: <h3><font color=#e00000>Cryptographic Transforms</font></h3><p>
1.32 deraadt 238:
1.11 deraadt 239: Cryptographic Transforms are used to encrypt and decrypt data. These
240: are normally used with an encryption key for data encryption and with
241: a decryption key for data decryption. The security of a Cryptographic
242: Transform should rely only on the keying material.<p>
1.6 deraadt 243:
1.24 niklas 244: OpenBSD provides transforms like DES, 3DES, Blowfish and Cast for the
1.36 deraadt 245: kernel and userland programs, which are used in many places like:<p>
1.10 deraadt 246: <ul>
1.27 deraadt 247: <li>In libc for creating
1.71 jufi 248: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=blf_key">Blowfish</a>
249: passwords. See also the <a href="papers/bcrypt-paper.ps">USENIX paper</a>
1.33 deraadt 250: on this topic.
1.27 deraadt 251: <li>In
1.78 brad 252: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ipsec>IPSEC</a>
1.27 deraadt 253: to provide confidentiality for the network layer.
254: <li>In Kerberos and a handful of kerberized applications, like
255: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=telnet>telnet</a>,
256: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=cvs>cvs</a>,
257: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rsh>rsh</a>,
258: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rcp>rcp</a>,
259: and
260: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rlogin>rlogin</a>.
1.44 provos 261: <li>In <a href=http://www.physnet.uni-hamburg.de/provos/photuris/>
1.27 deraadt 262: photurisd</a> and
263: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd>isakmpd</a>
1.78 brad 264: to protect the exchanges where IPSEC key material is negotiated.
1.24 niklas 265: <li>In AFS to protect the messages passing over the network, providing
1.27 deraadt 266: confidentiality of remote filesystem access.
1.24 niklas 267: <li>In libssl to let applications communicate over the de-facto standard
268: cryptographically secure SSL protocol.
1.10 deraadt 269: </ul>
1.1 deraadt 270:
1.10 deraadt 271: <p>
1.51 deraadt 272: <a name=hardware></a>
273: <h3><font color=#e00000>Cryptographic Hardware Support</font></h3><p>
274:
1.58 louis 275: OpenBSD, starting with 2.7, has begun supporting some cryptography hardware
276: such as accelerators and random number generators.
1.51 deraadt 277: <ul>
278: <li><b>IPSEC crypto dequeue</b><br>
279: Our IPSEC stack has been modified so that cryptographic functions get
280: done out-of-line. Most simple software IPSEC stacks need to do
281: cryptography when processing each packet. This results in syncronous
1.73 aaron 282: performance. To use hardware properly and speedily one needs to separate
1.51 deraadt 283: these two components, as we have done. Actually, doing this gains some
284: performance even for the software case.
285: <p>
1.80 deraadt 286: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=hifn&sektion=4">
287: HiFn 7751</a></b><br>
1.56 deraadt 288: Cards using the <a href="http://www.hifn.com/products/7751.html">HiFn 7751</a>
1.69 deraadt 289: can be used as a symmetric cryptographic accelerator (ie.
1.51 deraadt 290: <a href="http://www.powercrypt.com">PowerCrypt</a>).
291: Current performance using a single Hifn 7751 on each end of a tunnel
292: is 63Mbit/sec for 3DES/SHA1 ESP, nearly a 600% improvement over
293: using a P3/550 cpu. Further improvements are under way to resolve a
294: few more issues, but as of April 13, 2000 the code is considered
1.53 deraadt 295: stable. We wrote our own driver for supporting this chip, rather
296: than using the (USA-written)
297: <a href="http://www.powercrypt.com">powercrypt</a> driver, as well
1.60 deraadt 298: our driver links in properly to the IPSEC stack.
1.53 deraadt 299: The 7751 is now considered slow by industry standards and many vendors
300: have faster chips (even HiFn now has a faster but more expensive
1.60 deraadt 301: chip). Peak performance with 3DES SHA1 ESP is around 63MBit/sec.
302: <p>
303: (As an aside, HiFn was a difficult company to deal with; they even
304: threatened to sue us over our non-USA reverse engineering of their
305: crypto unlock algorithm).
1.53 deraadt 306: <p>
1.69 deraadt 307:
308: <li><b>Hifn 6500</b><br>
309: This device is an assymetric crypto unit. It has support for RSA, DSA,
310: and DH algorithms, as well as other major big number functions. It also
311: contains a very high performance random number generator. We have one
312: device, full documention, and sample code. Development has not yet
313: started.
314: <p>
315:
1.80 deraadt 316: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ubsec&sektion=4">
317: Broadcom BCM5805 (or beta chip Bluesteelnet 5501)</a></b><br>
1.65 deraadt 318: Just after the OpenBSD 2.7 release, we succeeded at adding preliminary
319: support for these early release parts provided to us by the vendor,
1.76 deraadt 320: specifically starting with the test chip 5501.
1.69 deraadt 321: These devices provide the highest performance symmetric cryptography
322: we have seen.
323: <p>
1.59 deraadt 324: Bluesteelnet was bought by Broadcom and started making real parts.
1.65 deraadt 325: Their new BCM5805 is similar, except that they also add an asymetric
326: engine for running DSA, RSA, and other such algorithms. With approximate
327: performance starting at more than four times as fast as the HiFn,
328: hopefully this chip will become more common soon.
1.60 deraadt 329: <p>
330: The Broadcom/Bluesteelnet people have been great to deal with. They gave
1.69 deraadt 331: us complete documentation and sample code for their chips and a
332: sufficient number of cards to test with.
1.60 deraadt 333: <p>
1.74 deraadt 334: Post 2.8, this driver was also modified to generate random numbers on
335: the BCM5805 and similar versions, and feed that data into the kernel
336: entropy pool.
337: <p>
1.60 deraadt 338:
1.80 deraadt 339: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ises&sektion=4">
340: Pijnenburg PCC-ISES</a></b><br>
1.60 deraadt 341: The <a href="http://www.pcc.pijnenburg.nl/pcc-ises.htm">PCC-ISES</a> is a
342: new chipset from the Netherlands. We have received sample hardware and
1.74 deraadt 343: documentation, and work on a driver is in progress. At the moment, the
344: driver is capable of feeding random numbers into the kernel entropy pool.
1.60 deraadt 345: <p>
346:
1.72 deraadt 347: <li><b>SafeNet 2141</b><br>
1.60 deraadt 348: We have received documentation and sample hardware for the
1.72 deraadt 349: <a href="http://www.safenet-inc.com/OEM/OEMTechnologyDefault.htm">SafeNet</a>
350: crypto cards. Work to support at least the symmetric cryptography of
351: these devices has started.
1.57 deraadt 352: <p>
353:
1.80 deraadt 354: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=txp&sektion=4">
355: 3com 3c990</a></b><br>
1.77 deraadt 356: 3com gave us a driver to support the ethernet component of this chipset,
1.79 ericj 357: and based on that, we have written our own ethernet driver. This driver
358: has now been integrated once we were able to get a free license on the
359: microcode. We have have also received (all?) the information needed for
360: supporting the cryptographic functions, which will require a little bit of
361: IPSEC subsystem rearranging. Check back later..
1.69 deraadt 362: <p>
363:
364: <li><b>Intel IPSEC card</b><br>
1.77 deraadt 365: Much like Intel does for all their networking division components, and
366: completely unlike most other vendors, Intel steadfastly refuse to provide
367: us with documentation. We have talked to about five technical people who
368: are involved in the development of those products. They all want us to
369: have documentation. They commend us on what we have done. But their hands
370: are tied by management who does not perceive a benefit to themselves for
371: providing documentation. Forget about Intel. (If you want to buy gigabit
372: ethernet hardware, we recommend anything else... for the same reason:
373: most drivers we have for Intel networking hardware were written without
374: documentation).
1.52 deraadt 375: <p>
1.69 deraadt 376:
1.80 deraadt 377: <li><b><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pchb&sektion=4">
378: Intel 82802AB/82802AC Firmware Hub RNG</a></b><br>
1.74 deraadt 379: The 82802 FWH chip (found on i810, i820, i840, i850, and i860 motherboards)
380: contains a random number generator (RNG). High-performance IPSEC
381: requires more random number entropy. As of April 10, 2000, we support
382: the RNG. We will add support for other RNG's found on crypto chips.
1.69 deraadt 383: <p>
384:
1.52 deraadt 385: <li><b>OpenSSL</b><br>
386: We have grand schemes for supporting crypto cards that can do RSA or DSA,
387: and exporting the functions of all crypto cards to OpenSSL so that
388: userland programs (ie. <a href="http://www.openssh.com">ssh</a>,
389: <a href="http://www.modssl.org/">apache https</a>, etc)
390: can benefit.
1.51 deraadt 391: </ul>
392:
393: <p>
1.69 deraadt 394: <b>If people wish to help with writing drivers,
395: <a href=#people>come and help us</a>.</b>
396:
397: <p>
1.32 deraadt 398: <a name=people></a>
1.42 deraadt 399: <h3><font color=#e00000>International Cryptographers Wanted</font></h3><p>
1.32 deraadt 400:
401: Of course, our project needs people to work on these systems. If any
402: non-American cryptographer who meets the constraints listed earlier is
403: interested in helping out with embedded cryptography in OpenBSD,
404: please contact us.<p>
405:
1.33 deraadt 406: <p>
407: <a name=papers></a>
1.42 deraadt 408: <h3><font color=#e00000>Further Reading</font></h3><p>
1.33 deraadt 409:
410: A number of papers have been written by OpenBSD team members, about
411: cryptographic changes they have done in OpenBSD. The postscript
1.34 deraadt 412: versions of these documents are available as follows.<p>
1.33 deraadt 413:
414: <ul>
1.43 deraadt 415: <li>A Future-Adaptable Password Scheme.<br>
1.49 deraadt 416: <a href=events.html#usenix99>Usenix 1999</a>,
1.71 jufi 417: by <a href=mailto:provos@openbsd.org>Niels Provos</a>,
1.43 deraadt 418: <a href=mailto:dm@openbsd.org>David Mazieres</a>.<br>
1.33 deraadt 419: <a href=papers/bcrypt-paper.ps>paper</a> and
420: <a href=papers/bcrypt-slides.ps>slides</a>.
1.43 deraadt 421: <p>
422: <li>Cryptography in OpenBSD: An Overview.<br>
1.49 deraadt 423: <a href=events.html#usenix99>Usenix 1999</a>,
1.43 deraadt 424: by <a href=mailto:deraadt@openbsd.org>Theo de Raadt</a>,
425: <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a>,
426: <a href=mailto:art@openbsd.org>Artur Grabowski</a>,
427: <a href=mailto:angelos@openbsd.org>Angelos D. Keromytis</a>,
428: <a href=mailto:provos@openbsd.org>Niels Provos</a>.<br>
1.33 deraadt 429: <a href=papers/crypt-paper.ps>paper</a> and
430: <a href=papers/crypt-slides.ps>slides</a>.
1.62 niklas 431: <p>
432: <li>Implementing Internet Key Exchange (IKE).<br>
433: <a href=events.html#usenix2000>Usenix 2000</a>,
434: by <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a> and
435: <a href=mailto:angelos@openbsd.org>Angelos D. Keromytis</a>.<br>
436: <a href=papers/ikepaper.ps>paper</a> and
437: <a href=papers/ikeslides.ps>slides</a>.
1.63 deraadt 438: <p>
439: <li>Encrypting Virtual Memory</a><br>
440: <a href=events.html#sec2000>Usenix Security 2000</a>,
441: <a href=mailto:provos@openbsd.org>Niels Provos</a>.<br>
1.64 provos 442: <a href=papers/swapencrypt.ps>paper</a> and
443: <a href=papers/swapencrypt-slides.ps>slides</a>.
1.33 deraadt 444: </ul>
445:
1.32 deraadt 446: <p>
1.1 deraadt 447: <hr>
1.75 wvdputte 448: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.10 deraadt 449: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
450: <br>
1.81 ! hin 451: <small>$OpenBSD: crypto.html,v 1.80 2001/05/09 11:49:20 deraadt Exp $</small>
1.1 deraadt 452:
1.10 deraadt 453: </body>
454: </html>