OpenSSL STATUS Last modified at
- ______________ $Date: 2000/02/27 14:44:43 $
+ ______________ $Date: 2000/07/02 21:11:11 $
DEVELOPMENT STATE
- o OpenSSL 0.9.5: Under development...
- 0.9.5-beta1 was available.
- Debian GNU/Linux 2.1 - test passed
- Mingw32 egcs 1.1.2 - test passed
- FreeBSD 3.0-RELEASE - test passed
- FreeBSD 3.2-RELEASE - test passed
- solaris-sparcv9-cc - test passed
- solaris-sparcv9-gcc - test passed
- hpux-parisc-gcc - test passed
- AIX 4.3 (aix-cc) - test passed
- VC++ - test passed
- 0.9.5beta2 is available.
- FreeBSD 3.0-RELEASE - test passed
- Proposed release time: Monday, February 28th 2000
+ o OpenSSL 0.9.6: Under development...
+ 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
AVAILABLE PATCHES
- o shared libraries <behnke@trustcenter.de>
o CA.pl patch (Damien Miller)
IN PROGRESS
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.
- Documentation for the openssl utility.
+ 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.
NEEDS PATCH
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).
-
- o ERR_error_string(..., buf) does not know how large buf is,
- there should be ERR_error_string_n(..., buf, bufsize)
- or similar.
-
WISHES
o