OpenSSL STATUS Last modified at
- ______________ $Date: 1999/02/20 16:50:53 $
+ ______________ $Date: 2000/09/24 15:42:34 $
DEVELOPMENT STATE
- o OpenSSL 0.9.2: Still under development.
- Proposed freeze time: Monday, March 8th 1999
- Proposed release time: Monday, March 15th 1999
- o OpenSSL 0.9.1c: Released on December 23th, 1998
+ o OpenSSL 0.9.6: Released on September 24th, 2000
+ o OpenSSL 0.9.5a: Released on April 1st, 2000
+ o OpenSSL 0.9.5: Released on February 28th, 2000
+ o OpenSSL 0.9.4: Released on August 09th, 1999
+ o OpenSSL 0.9.3a: Released on May 29th, 1999
+ o OpenSSL 0.9.3: Released on May 25th, 1999
+ o OpenSSL 0.9.2b: Released on March 22th, 1999
+ o OpenSSL 0.9.1c: Released on December 23th, 1998
RELEASE SHOWSTOPPERS
AVAILABLE PATCHES
+ o CA.pl patch (Damien Miller)
+
IN PROGRESS
- o Steve is currently working on:
- X509 V3 extension code including:
- 1. Support for the more common PKIX extensions.
- 2. Proper (or at least usable) certificate chain verification.
- 3. Support in standard applications (req, x509, ca).
- 4. Documentation on how all the above works.
- Next on the list is probably PKCS#12 integration.
-
- o Mark is currently working on:
- Folding in any changes that are in the C2Net code base that were
- not in the original SSLeay-0.9.1.b release. Plus other minor
- tidying.
-
- o Ralf is currently working on:
- 1. Support for SSL_set_default_verify_paths(),
- SSL_load_verify_locations(), SSL_get_cert_store() and
- SSL_set_cert_store() functions which work like their existing
- SSL_CTX_xxx() variants but on a per connection basis. That's needed
- to let us provide full-featured per-URL client verification in
- mod_ssl or Apache-SSL.
- 2. The perl/ stuff to make it really work the first time ;-)
- 3. The new documentation set in PID format under doc/
- 4. More cleanups to get rid of obsolete/old/ugly files in the
- source tree which are not really needed.
+ o Steve is currently working on (in no particular order):
+ ASN1 code redesign, butchery, replacement.
+ EVP cipher enhancement.
+ Proper (or at least usable) certificate chain verification.
+ Private key, certificate and CRL API and implementation.
+ Developing and bugfixing PKCS#7 (S/MIME code).
+ Various X509 issues: character sets, certificate request extensions.
+ o Geoff and Richard are currently working on:
+ ENGINE (the new code that gives hardware support among others).
+ o Richard is currently working on:
+ UTIL (a new set of library functions to support some higher level
+ functionality that is currently missing).
+ Dynamic thread-lock support.
+ Shared library support for VMS.
NEEDS PATCH
+ o non-blocking socket on AIX
+ o $(PERL) in */Makefile.ssl
+ o "Sign the certificate?" - "n" creates empty certificate file
+
OPEN ISSUES
+ o internal_verify doesn't know about X509.v3 (basicConstraints
+ CA flag ...)
+
o The Makefile hierarchy and build mechanism is still not a round thing:
1. The config vs. Configure scripts
itself. Then we can avoid a lot of those platform checks
which are currently in Configure.
- 2. The xxx.org -> xxx.h generation:
- It's not obvious for which file xxx.org is the source.
- Suggestion: Rename xxx.org to xxx.h.in (Autoconf style), this way
- one sees that xxx.h.in is the input for xxx.h
-
- Status: Mark +1
-
- o The installation under "make install" produces a very
- installation layout: $prefix/certs and $prefix/private dirs. That's
- not nice. Ralf suggests to move the two certs and private dirs either
- to $prefix/etc/, $prefix/lib/ or $prefix/share. Alternatively
- we could also not install the certs at all.
-
- Status: Ralf +1 for both not installing the certs at all and
- moving it to $prefix/etc/. +0 for $prefix/lib/
- and $prefix/share.
- Paul: why is it not nice?
- Ralf: because it messes up the install dir when
- $prefix is not a dedicated area like /usr/local/ssl.
- When we move them to a standard subdir like
- etc/ lib/ or share/ we don't mess up things
- when $prefix is /usr or /usr/local, etc.
- Additionally it makes package vendors life
- easier....
-
o Support for Shared Libraries has to be added at least
for the major Unix platforms. The details we can rip from the stuff
Ralf has done for the Apache src/Configure script. Ben wants the
compiler PIC and linker DSO flags from Apache
into the OpenSSL Configure script.
+ Ulf: +1 for using GNU autoconf and libtool (but not automake,
+ which apparently is not flexible enough to generate
+ libcrypto)
+
+
o The perl/ stuff needs a major overhaul. Currently it's
totally obsolete. Either we clean it up and enhance it to be up-to-date
with the C code or we also could replace it with the really nice
to date.
Paul +1
- o The EVP and ASN1 stuff is a mess. Currently you have one EVP_CIPHER
- structure for each cipher. This may make sense for things like DES but
- for variable length ciphers like RC2 and RC4 it is NBG. Need a way to
- use the EVP interface and set up the cipher parameters. The ASN1 stuff
- is also foo wrt ciphers whose AlgorithmIdentifier has more than just
- an IV in it (e.g. RC2, RC5). This also means that EVP_Seal and EVP_Open
- don't work unless the key length matches the fixed value (some vendors
- use a key length decided by the size of the RSA encrypted key and expect
- RC2 to adapt).
-
WISHES
- o Damien Miller:
- "How about making the each of the locations compile-time defined. I
- would like to (for example) put binaries in /usr/bin, configuration
- data, certs and keys in /etc/openssl/certs and /etc/openssl/keys, etc.
- This would also be a great boon to binary package makers. The
- SSLeay-0.9.1b RPM already includes some patches which do some of this.
- I can forward them if you wish."
-
+ o