Annotation of www/crypto.html, Revision 1.59
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>
19: "The mantra of any good security engineer is: "Security is a not a
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
74: extended to make use of Kerberos IV as well. Kerberos V support will
1.54 deraadt 75: appear sometime in 2000, but at present time a freely exportable
1.16 deraadt 76: Kerberos V release does not exist.<p>
77:
1.15 deraadt 78: Today cryptography is an important means for enhancing the <a
79: href=security.html>security</a> of an operating system. The
1.42 deraadt 80: cryptography utilized in OpenBSD can be classified into various
81: aspects, described as follows.<p>
1.10 deraadt 82:
1.39 louis 83: <a name=ssh></a>
1.47 provos 84: <h3><font color=#e00000>OpenSSH</font></h3><p>
1.39 louis 85:
1.40 deraadt 86: What is the first thing most people do after installing OpenBSD?
1.55 deraadt 87: They install Secure Shell
88: (<a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ssh>ssh</a>)
1.46 deraadt 89: from the ports tree or the packages on the FTP sites. Until now, that is.<p>
1.39 louis 90:
1.55 deraadt 91: As of the 2.6 release, OpenBSD contains
1.50 provos 92: <a href="http://www.openssh.com/">OpenSSH</a>, an absolutely free and
93: patent unencumbered version of ssh.
1.55 deraadt 94: As of the OpenBSD 2.6 release date,
95: <a href="http://www.openssh.com/">OpenSSH</a> interoperated with ssh
96: version 1 and had many added features,
1.47 provos 97: <ul>
98: <li>
99: all components of a restrictive nature (ie. patents, see
100: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ssl>ssl</a>))
1.55 deraadt 101: had been directly removed from the source code; any licensed or
102: patented components used external libraries.
1.47 provos 103: </li>
104: <li>
1.55 deraadt 105: had been updated to support ssh protocol 1.5.
1.47 provos 106: </li>
107: <li>
1.55 deraadt 108: contained added support for
1.47 provos 109: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=kerberos>kerberos</a>
110: authentication and ticket passing.
111: </li>
112: <li>
1.55 deraadt 113: supported one-time password authentication with
1.47 provos 114: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=skey>skey</a>.
115: </li>
116: </ul>
117: <p>
118:
1.55 deraadt 119: Roughly, we took a free license release of ssh and OpenBSD-ifyed it.
120: We get around the USA-based RSA patent by providing an easy way to
1.47 provos 121: automatically download and install a RSA-enabled package containing
122: shared library versions of libcrypto and libssl. These packages are
123: based on OpenSSL. People living outside the USA can freely use the
1.40 deraadt 124: RSA patented code, while people inside the USA can freely use it for
1.47 provos 125: non-commercial purposes. It appears as if companies inside the USA
126: can use the RSA libraries too, as long as RSA is not used in a profit
127: generating role.<p>
1.39 louis 128:
1.55 deraadt 129: But this way almost everyone will get ssh built into their OS.<p>
130:
131: <strong>NEW! OpenSSH supports protocol 2.0!</strong><p>
132:
133: Recently, we have extended OpenSSH so that it also does SSH 2 protocol.
134: Having a ssh daemon which can do all 3 major SSH protocols
135: (1.3, 1.5, 2.0) permits us much flexibility. Protocol 2.0 does not
136: use RSA for it's public key cryptography, relying instead on the DH
137: and DSA algorithms. In OpenBSD 2.7 -- which will ship with the new
138: OpenSSH -- you get protocol 2.0 support right out of the box! If
139: you wish to also support protocol 1.3 and 1.5, you simply add the
140: RSA package (as described our
141: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ssl>ssl</a>
142: manual page), and restart the daemon.
1.39 louis 143:
1.18 deraadt 144: <a name=prng></a>
1.42 deraadt 145: <h3><font color=#e00000>Pseudo Random Number Generators</font></h3><p>
1.32 deraadt 146:
1.10 deraadt 147: A Pseudo Random Number Generator (PRNG) provides applications with a stream of
148: numbers which have certain important properties for system security:<p>
149:
150: <ul>
1.11 deraadt 151: <li>It should be impossible for an outsider to predict the output of the
152: random number generator even with knowledge of previous output.
153: <li>The generated numbers should not have repeating patterns which means
154: the PRNG should have a very long cycle length.
1.10 deraadt 155: </ul>
1.32 deraadt 156: <p>
1.10 deraadt 157:
1.13 deraadt 158: A PRNG is normally just an algorithm where the same initial starting
159: values will yield the same sequence of outputs. On a multiuser
160: operating system there are many sources which allow seeding the PRNG
161: with random data. The OpenBSD kernel uses the mouse interrupt timing,
162: network data interrupt latency, inter-keypress timing and disk IO
163: information to fill an entropy pool. Random numbers are available for
164: kernel routines and are exported via devices to userland programs.
1.36 deraadt 165: So far random numbers are used in the following places:<p>
1.13 deraadt 166:
1.10 deraadt 167: <ul>
1.14 deraadt 168: <li>Dynamic sin_port allocation in bind(2).
169: <li>PIDs of processes.
1.26 aaron 170: <li>IP datagram IDs.
1.14 deraadt 171: <li>RPC transaction IDs (XID).
172: <li>NFS RPC transaction IDs (XID).
173: <li>DNS Query-IDs.
174: <li>Inode generation numbers, see getfh(2) and fsirand(8).
1.31 aaron 175: <li>Timing perturbance in traceroute(8).
1.14 deraadt 176: <li>Stronger temporary names for mktemp(3) and mkstemp(3)
177: <li>Randomness added to the TCP ISS value for protection against
178: spoofing attacks.
1.29 deraadt 179: <li>random padding in IPSEC esp_old packets.
1.14 deraadt 180: <li>To generate salts for the various password algorithms.
181: <li>For generating fake S/Key challenges.
1.44 provos 182: <li>In <a href=http://www.physnet.uni-hamburg.de/provos/photuris/>photurisd</a>
1.28 angelos 183: and <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd>isakmpd</a>
184: to provide liveness proof of key exchanges.
1.10 deraadt 185: </ul>
1.1 deraadt 186:
1.10 deraadt 187: <p>
1.18 deraadt 188: <a name=hash></a>
1.42 deraadt 189: <h3><font color=#e00000>Cryptographic Hash Functions</font></h3><p>
1.32 deraadt 190:
1.10 deraadt 191: A Hash Function compresses its input data to a string of
1.36 deraadt 192: constant size. For a Cryptographic Hash Function it is infeasible to find:
193:
1.1 deraadt 194: <ul>
1.11 deraadt 195: <li>two inputs which have the same output (collision resistant),
196: <li>a different input for a given input with the same output
197: (2nd preimage resistant).
1.1 deraadt 198: </ul>
1.32 deraadt 199: <p>
1.10 deraadt 200:
1.12 millert 201: In OpenBSD MD5, SHA1, and RIPEMD-160 are used as Cryptographic Hash Functions,
1.36 deraadt 202: e.g:<p>
1.10 deraadt 203: <ul>
1.27 deraadt 204: <li>In <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=skey>S/Key</a>
205: to provide one time passwords.
206: <li>In <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ipsec>IPsec</a>,
1.44 provos 207: <a href=http://www.physnet.uni-hamburg.de/provos/photuris/>photurisd</a>
1.27 deraadt 208: and
209: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd>isakmpd(8)</a>
210: to authenticate the data origin of packets and to ensure packet integrity.
211: <li>For FreeBSD-style MD5 passwords (not enabled by default), see
212: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=passwd.conf&sektion=5>
213: passwd.conf(5)</a>
214: <li>For TCP SYN cookie support (not enabled by default), see
215: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=options&sektion=4>
216: options(4)</a>
1.24 niklas 217: <li>In libssl for digital signing of messages.
1.10 deraadt 218: </ul>
1.32 deraadt 219: <p>
1.10 deraadt 220:
1.6 deraadt 221: <p>
1.18 deraadt 222: <a name=trans></a>
1.42 deraadt 223: <h3><font color=#e00000>Cryptographic Transforms</font></h3><p>
1.32 deraadt 224:
1.11 deraadt 225: Cryptographic Transforms are used to encrypt and decrypt data. These
226: are normally used with an encryption key for data encryption and with
227: a decryption key for data decryption. The security of a Cryptographic
228: Transform should rely only on the keying material.<p>
1.6 deraadt 229:
1.24 niklas 230: OpenBSD provides transforms like DES, 3DES, Blowfish and Cast for the
1.36 deraadt 231: kernel and userland programs, which are used in many places like:<p>
1.10 deraadt 232: <ul>
1.27 deraadt 233: <li>In libc for creating
234: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=blf_key>Blowfish</a>
1.33 deraadt 235: passwords. See also the <a href=papers/bcrypt-paper.ps>USENIX paper</a>
236: on this topic.
1.27 deraadt 237: <li>In
238: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=ipsec>IPsec</a>
239: to provide confidentiality for the network layer.
240: <li>In Kerberos and a handful of kerberized applications, like
241: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=telnet>telnet</a>,
242: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=cvs>cvs</a>,
243: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rsh>rsh</a>,
244: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rcp>rcp</a>,
245: and
246: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rlogin>rlogin</a>.
1.44 provos 247: <li>In <a href=http://www.physnet.uni-hamburg.de/provos/photuris/>
1.27 deraadt 248: photurisd</a> and
249: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd>isakmpd</a>
250: to protect the exchanges where IPsec key material is negotiated.
1.24 niklas 251: <li>In AFS to protect the messages passing over the network, providing
1.27 deraadt 252: confidentiality of remote filesystem access.
1.24 niklas 253: <li>In libssl to let applications communicate over the de-facto standard
254: cryptographically secure SSL protocol.
1.10 deraadt 255: </ul>
1.1 deraadt 256:
1.10 deraadt 257: <p>
1.51 deraadt 258: <a name=hardware></a>
259: <h3><font color=#e00000>Cryptographic Hardware Support</font></h3><p>
260:
1.58 louis 261: OpenBSD, starting with 2.7, has begun supporting some cryptography hardware
262: such as accelerators and random number generators.
1.51 deraadt 263: <ul>
264: <li><b>IPSEC crypto dequeue</b><br>
265: Our IPSEC stack has been modified so that cryptographic functions get
266: done out-of-line. Most simple software IPSEC stacks need to do
267: cryptography when processing each packet. This results in syncronous
268: performance. To use hardware properly and speedily one needs to seperate
269: these two components, as we have done. Actually, doing this gains some
270: performance even for the software case.
271: <p>
272: <li><b>HiFn 7751</b><br>
1.56 deraadt 273: Cards using the <a href="http://www.hifn.com/products/7751.html">HiFn 7751</a>
1.53 deraadt 274: can be used as a cryptographic accelerator (ie.
1.51 deraadt 275: <a href="http://www.powercrypt.com">PowerCrypt</a>).
276: Current performance using a single Hifn 7751 on each end of a tunnel
277: is 63Mbit/sec for 3DES/SHA1 ESP, nearly a 600% improvement over
278: using a P3/550 cpu. Further improvements are under way to resolve a
279: few more issues, but as of April 13, 2000 the code is considered
1.53 deraadt 280: stable. We wrote our own driver for supporting this chip, rather
281: than using the (USA-written)
282: <a href="http://www.powercrypt.com">powercrypt</a> driver, as well
283: our driver links in properly to the IPSEC stack<p>
284: The 7751 is now considered slow by industry standards and many vendors
285: have faster chips (even HiFn now has a faster but more expensive
1.57 deraadt 286: chip).
1.53 deraadt 287: <p>
1.59 ! deraadt 288: <li><b>Broadcom BCM5805 (or beta chip Bluesteelnet 5501)</b><br>
1.57 deraadt 289: Just after the OpenBSD 2.7 release, we succeeded at adding support
290: for these early release parts provided to us by the vendor, specifically
1.59 ! deraadt 291: starting with the test chip
! 292: <a href="http://www.bluesteelnet.com/product.html">5501</a>.
! 293: Bluesteelnet was bought by Broadcom and started making real parts.
! 294: The new BCM5805 is similar, except that they also add an asymetric engine
1.57 deraadt 295: for running DSA, RSA, and other such algorithms. With approximate
296: performance starting at more than twice as fast as the HiFn, hopefully
1.59 ! deraadt 297: this chip will become more common soon. We have not fully optimized our
! 298: driver yet, so performance figures will be forthcoming.
1.57 deraadt 299: <p>
300:
301: <li><b>Other cards</b><br>
302: We are moving towards supporting other chips such as:
1.53 deraadt 303: <ul>
304: <li><a href="http://www.ire.com/OEM/OEMTechnologyDefault.htm">IRE 2141</a>
305: <li><a href="http://www.pcc.pijnenburg.nl/pcc-ises.htm">Pijnenburg PCC-ISES</a>
306: <li>perhaps the
307: <a href="http://www.3com.com/promotions/3c990promo/index.html">3com 3c990</a>
308: <li>and others
309: </ul>
310: <p>
1.57 deraadt 311: Of these, IRE in particular has already been very friendly, and have given
312: us all the information we need to support their hardware. Other vendors
313: are on our list, but we are focusing on the fast+cheap solutions first.
1.52 deraadt 314: Intel (and 3com to a lesser degree) don't yet fully understand how
315: they could benefit from giving us documentation for their cryptography
316: cards, so feel free to contact them independently and encourage them.
317: <p>
318: If people wish to help with writing drivers,
1.51 deraadt 319: <a href=#people>come and help us</a>.
320: <p>
321: <li><b>Intel 82802AB/82802AC Firmware Hub RNG</b><br>
322: The 82802 FWH chip (found on i810, i820, and i840 motherboards) contains
323: a random number generator (RNG). High-performance IPSEC requires more
324: random number entropy. As of April 10, 2000, we support the RNG. We
325: will add support for other RNG's found on crypto chips.
1.52 deraadt 326: <p>
327: <li><b>OpenSSL</b><br>
328: We have grand schemes for supporting crypto cards that can do RSA or DSA,
329: and exporting the functions of all crypto cards to OpenSSL so that
330: userland programs (ie. <a href="http://www.openssh.com">ssh</a>,
331: <a href="http://www.modssl.org/">apache https</a>, etc)
332: can benefit.
1.51 deraadt 333: </ul>
334:
335: <p>
1.32 deraadt 336: <a name=people></a>
1.42 deraadt 337: <h3><font color=#e00000>International Cryptographers Wanted</font></h3><p>
1.32 deraadt 338:
339: Of course, our project needs people to work on these systems. If any
340: non-American cryptographer who meets the constraints listed earlier is
341: interested in helping out with embedded cryptography in OpenBSD,
342: please contact us.<p>
343:
1.33 deraadt 344: <p>
345: <a name=papers></a>
1.42 deraadt 346: <h3><font color=#e00000>Further Reading</font></h3><p>
1.33 deraadt 347:
348: A number of papers have been written by OpenBSD team members, about
349: cryptographic changes they have done in OpenBSD. The postscript
1.34 deraadt 350: versions of these documents are available as follows.<p>
1.33 deraadt 351:
352: <ul>
1.43 deraadt 353: <li>A Future-Adaptable Password Scheme.<br>
1.49 deraadt 354: <a href=events.html#usenix99>Usenix 1999</a>,
1.43 deraadt 355: by <a href=mailto:provos@openbsd.org>Niels Provos<a/>,
356: <a href=mailto:dm@openbsd.org>David Mazieres</a>.<br>
1.33 deraadt 357: <a href=papers/bcrypt-paper.ps>paper</a> and
358: <a href=papers/bcrypt-slides.ps>slides</a>.
1.43 deraadt 359: <p>
360: <li>Cryptography in OpenBSD: An Overview.<br>
1.49 deraadt 361: <a href=events.html#usenix99>Usenix 1999</a>,
1.43 deraadt 362: by <a href=mailto:deraadt@openbsd.org>Theo de Raadt</a>,
363: <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a>,
364: <a href=mailto:art@openbsd.org>Artur Grabowski</a>,
365: <a href=mailto:angelos@openbsd.org>Angelos D. Keromytis</a>,
366: <a href=mailto:provos@openbsd.org>Niels Provos</a>.<br>
1.33 deraadt 367: <a href=papers/crypt-paper.ps>paper</a> and
368: <a href=papers/crypt-slides.ps>slides</a>.
369: </ul>
370:
1.32 deraadt 371: <p>
1.1 deraadt 372: <hr>
1.19 pauls 373: <a href=/index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.10 deraadt 374: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
375: <br>
1.59 ! deraadt 376: <small>$OpenBSD: crypto.html,v 1.58 2000/06/16 17:51:37 louis Exp $</small>
1.1 deraadt 377:
1.10 deraadt 378: </body>
379: </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