===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/crypto.html,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -r1.141 -r1.142
--- www/crypto.html 2014/04/30 08:44:43 1.141
+++ www/crypto.html 2014/05/02 18:55:39 1.142
@@ -39,17 +39,8 @@
We do not directly use cryptography with nasty patents.
We also require that such software is from countries with useful export
licenses because we do not wish to break the laws of any country.
-The cryptographic software components which we use currently were
-written in Argentina, Australia, Canada, Germany, Greece, Norway, and
-Sweden.
-When we create OpenBSD releases or snapshots we build our release
-binaries in free countries to assure that the sources and binaries we
-provide to users are free of tainting. In the past our release binary
-builds have been done in Canada, Sweden, and Germany.
-
-
OpenBSD was the first operating system to ship with an IPsec stack.
We've been including IPsec since the OpenBSD 2.1 release in 1997.
@@ -107,27 +98,7 @@
network data interrupt latency, inter-keypress timing and disk IO
information to fill an entropy pool. Random numbers are available for
kernel routines and are exported via devices to userland programs.
-So far random numbers are used in the following places:
-
-- Dynamic sin_port allocation in bind(2).
-
- PIDs of processes.
-
- IP datagram IDs.
-
- RPC transaction IDs (XID).
-
- NFS RPC transaction IDs (XID).
-
- DNS Query-IDs.
-
- Inode generation numbers, see getfh(2) and fsirand(8).
-
- Timing perturbance in traceroute(8).
-
- Stronger temporary names for mktemp(3) and mkstemp(3)
-
- Randomness added to the TCP ISS value for protection against
- spoofing attacks.
-
- random padding in IPsec esp_old packets.
-
- To generate salts for the various password algorithms.
-
- For generating fake S/Key challenges.
-
- In isakmpd(8)
- to provide liveness proof of key exchanges.
-
-
Cryptographic Hash Functions
@@ -142,23 +113,7 @@
-In OpenBSD MD5, SHA1, and RIPEMD-160 are used as Cryptographic Hash Functions,
-e.g:
-
-- In S/Key(1)
- to provide one time passwords.
-
- In IPsec(4)
- and
- isakmpd(8)
- to authenticate the data origin of packets and to ensure packet integrity.
-
- For FreeBSD-style MD5 passwords (not enabled by default), see
-
- login.conf(5)
-
- In libssl for digital signing of messages.
-
-
-
Cryptographic Transforms
@@ -166,230 +121,6 @@
are normally used with an encryption key for data encryption and with
a decryption key for data decryption. The security of a Cryptographic
Transform should rely only on the keying material.
-
-OpenBSD provides transforms like DES, 3DES, Blowfish and Cast for the
-kernel and userland programs, which are used in many places like:
-
-- In libc for creating
- Blowfish
- passwords. See also the USENIX paper
- on this topic.
-
- In
- IPsec(4)
- to provide confidentiality for the network layer.
-
- In isakmpd(8)
- to protect the exchanges where IPsec key material is negotiated.
-
- In libssl to let applications communicate over the de-facto standard
- cryptographically secure SSL protocol.
-
-
-
-
-
Cryptographic Hardware Support
-
-OpenBSD, starting with 2.7, has begun supporting some cryptography hardware
-such as accelerators and random number generators.
-
--
- IPsec crypto dequeue
- Our IPsec stack has been modified so that cryptographic functions get
- done out-of-line. Most simple software IPsec stacks need to do
- cryptography when processing each packet. This results in synchronous
- performance. To use hardware properly and speedily one needs to separate
- these two components, as we have done. Actually, doing this gains some
- performance even for the software case.
-
-
-
- Hifn 7751
- Cards using the Hifn 7751 can be used as a symmetric cryptographic
- accelerator, i.e., the
- Soekris VPN1201 or VPN1211
- (to buy)
- or
- PowerCrypt.
- Current performance using a single Hifn 7751 on each end of a tunnel
- is 64Mbit/sec for 3DES/SHA1 ESP, nearly a 600% improvement over
- using a P3/550 CPU. Further improvements are under way to resolve a
- few more issues, but as of April 13, 2000 the code is considered
- stable. We wrote our own driver for supporting this chip, rather
- than using the (USA-written)
- PowerCrypt driver, as well
- our driver links in properly to the IPsec stack.
- The 7751 is now considered slow by industry standards and many vendors
- have faster chips (even Hifn now has a faster but more expensive
- chip). Peak performance with 3DES SHA1 ESP is around 64Mbit/sec.
-
- After 2.9 shipped, support was added for the Hifn 7951 chip, a
- simplified version of the 7751 which adds a public key accelerator
- (unsupported) and a random number generator (supported). Cards
- were donated by Soekris Engineering.
-
- After 3.0 shipped, support was added for the Hifn 7811 chip, a
- faster version of the 7751 (around 130Mbit/s) with a random number
- generator. A card was donated by GTGI.
-
- After 3.2 shipped, support was added for the LZS compression algorithm
- used by ipcomp(4).
-
- After 3.4 shipped, support was added for the 7955 and 7956 chips.
- In addition to all the features of the previous 7951 chip, these add AES.
-
- Hifn was initially a difficult company to deal with (threatening to sue
- us over our non-USA reverse engineering of their crypto unlock algorithm),
- but more recently they have been very helpful in providing boards and
- support.
-
-
-
-
- Hifn 6500
- This device is an asymmetric crypto unit. It has support for RSA, DSA,
- and DH algorithms, as well as other major big number functions. It also
- contains a very high performance random number generator. We have one
- device, full documentation, and sample code. As of OpenBSD 3.1,
- both the random number generator and big number unit are working.
-
-
-
-
- Hifn 7814/7851/7854
- This device is a packet processor and asymmetric crypto unit. It has
- support for RSA, DSA, and DH algorithms, as well as other major big number
- functions and also has a random number generator. Currently, only the
- big number engine and the random number generator are supported (no
- packet transforms).
-
-
-
-
- Broadcom BCM5801/BCM5802/BCM5805/BCM5820/BCM5821/BCM5822/5823/5825/5860/5861/5862
- (or beta chip Bluesteelnet 5501/5601)
- Just after the OpenBSD 2.7 release, we succeeded at adding preliminary
- support for these early release parts provided to us by the vendor,
- specifically starting with the test chip 5501.
- These devices provide the highest performance symmetric cryptography
- we have seen.
-
- Bluesteelnet was bought by Broadcom and started making real parts.
- Their new BCM5805 is similar, except that they also add an asymmetric
- engine for running DSA, RSA, and other such algorithms. With approximate
- performance starting at more than four times as fast as the Hifn,
- hopefully this chip will become more common soon.
-
- The Broadcom/Bluesteelnet people have been great to deal with. They gave
- us complete documentation and sample code for their chips and a
- sufficient number of cards to test with.
-
- Post 2.8, this driver was also modified to generate random numbers on
- the BCM5805 and similar versions, and feed that data into the kernel
- entropy pool.
-
- Post 2.9, support was added for the BCM5820, which is mostly just a
- faster (64bit, higher clock speed) version of the BCM5805. Untested
- support for the BCM5821 was also added post 3.0.
-
- As of 3.1, the big num engine is supported, and RSA/DH/DSA operations
- can be accelerated.
-
- Support for the BCM5801, BCM5802, BCM5821 and BCM5822 was added before
- OpenBSD 3.2 (the untested BCM5821 support in 3.1 was broken because of
- some undocumented interrupt handling requirements).
-
- Partial support for BCM5823 was added for 3.4.
-
- Support for the BCM5825, BCM5860, BCM5861, and BCM5862 including support
- for AES with the BCM5823 or newer was added after 4.5.
-
-
-
-
- Securealink PCC-ISES
- The
- PCC-ISES is a new chipset from the Netherlands. We have received
- sample hardware and documentation, and work on a driver is in progress.
- At the moment, the driver is capable of feeding random numbers into
- the kernel entropy pool.
-
-
-
-
- SafeNet SafeXcel 1141/1741
- After 3.4 shipped, support was for added for these two chips (found on various
- SafeNet
- crypto cards. Supports DES, Triple-DES, AES, MD5, and SHA-1 symmetric crypto
- operations, RNG, public key operations, and full IPsec packet processing.
-
-
-
- SafeNet SafeXcel 1840
- We have received documentation and sample hardware for the
- SafeNet 1840
- crypto chip. Work to support at least the RNG and symmetric cryptography of
- these devices has started.
-
-
-
- SafeNet SafeXcel 2141
- We have received documentation and sample hardware for the
- SafeNet 2141
- crypto chip. Work to support at least the symmetric cryptography of
- these devices has started.
-
-
-
-
- 3com 3cr990
- 3com gave us a driver to support the ethernet component of this chipset,
- and based on that, we have written our own ethernet driver. This driver
- has now been integrated once we were able to get a free license on the
- microcode. Due to poor documentation and lack of cooperation (partly
- because of the high turnover rates at 3Com), the IPsec functions of the
- chip are not supported.... so this turned out to be a less than completely
- useful exercise.
-
-
-
- Intel IPsec card
- Much like Intel does for all their networking division components, and
- completely unlike most other vendors, Intel steadfastly refuses to provide
- us with documentation. We have talked to about five technical people who
- are involved in the development of those products. They all want us to
- have documentation. They commend us on what we have done. But their hands
- are tied by management who does not perceive a benefit to themselves for
- providing documentation. Forget about Intel. (If you want to buy gigabit
- ethernet hardware, we recommend anything else... for the same reason:
- most drivers we have for Intel networking hardware were written without
- documentation).
-
-
-
-
- Intel 82802AB/82802AC Firmware Hub RNG
- The 82802 FWH chip (found on i810, i820, i840, i850, and i860 motherboards)
- contains a random number generator (RNG). High-performance IPsec
- requires more random number entropy. As of April 10, 2000, we support
- the RNG. We will add support for other RNGs found on crypto chips.
-
-
-
- VIA C3 RNG
- The newer VIA C3 CPU contains a random number generator as an instruction.
- As of 3.3 this random number generator is used
- inside the kernel to feed the entropy pool.
-
-
-
- VIA C3 AES instructions
- VIA C3 CPUs with a step 8 or later Nehemiah core contains an AES
- implementation accessible via simple instructions. As of 3.4 the kernel supports them to be used in an
- IPsec context and exported by /dev/crypto. As of 3.5 performances have been greatly improved
- and OpenSSL now uses the new instruction directly when available
- without the need to enter the kernel, resulting in vastly
- improved speed (AES-128 measured at 780MByte/sec) for applications
- using OpenSSL to perform AES encryption.
-
-
-
- OpenSSL
- Years ago, we had a grand scheme to support crypto cards that can do
- RSA/DH/DSA automatically via OpenSSL calls. As of OpenBSD 3.2, that
- support works, and any card that is supported with such functionality
- will automatically use the hardware, including OpenSSH and httpd in
- SSL mode. No application changes are required.
-
-
-
-If people wish to help with writing drivers,
-come and help us.