OpenSSL STATUS Last modified at
- ______________ $Date: 1999/03/09 15:36:53 $
+ ______________ $Date: 1999/10/30 19:09:01 $
DEVELOPMENT STATE
- o OpenSSL 0.9.2: Freezed!
- - No more feature commits, please.
- - Commit bugfixes and cleanups only, please.
- - Already successfully tested platform:
- o FreeBSD 2.2.7 Ben Laurie OK
- o FreeBSD 3.1 Ralf S. Engelschall OK
- o Solaris 2.6 Ralf S. Engelschall ctype warns, test fails in test_ssl
- o Linux RH 5.1 Steve Henson OK
-
- Proposed release time: Monday, March 15th 1999
-
+ o OpenSSL 0.9.5: Under development...
+ 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
- o `make test' still fails under Solaris 2.6 in the test_ssl target
- o Compilation warnings: ctype-related int vs. char
- o Compilation error: "unsigned long*" and "int*" under AIX
-
AVAILABLE PATCHES
- o Solaris AS error (kenji@miyake.org)
+ o shared libraries <behnke@trustcenter.de>
o getenv in ca.c and x509_def.c (jaltman@watsun.cc.columbia.edu)
- o s3_lib.c - export clients (levitte@stacken.kth.se)
- o linux dynamic libs (colin@field.medicine.adelaide.edu.au)
- o MingW support (niklas@canit.se)
- o crypto/des/enc_read.c bugfix (mike@cs.mun.ca)
+ o SMIME tool (demo), Sampo Kellomaki <sampo@iki.fi>
+ o OCSP patch, Massimiliano Pala (madwolf@openca.org)
+ o CA.pl patch (Damien Miller)
+ o FreeBSD 3.0 changes (Richard Levitte)
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 Steve is currently working on (in no particular order):
+ Proper (or at least usable) certificate chain verification.
+ Private key, certificate and CRL API and implementation.
+ Checking and bugfixing PKCS#7 (S/MIME code).
+ Various X509 issues: character sets, certificate request extensions.
o Mark is currently working on:
Folding in any changes that are in the C2Net code base that were
NEEDS PATCH
+ o Arne Ansper: d2i_ASN1_bytes bug
+ o salzr@certco.com (Rich Salz): Bug in X509_name_print
+ <29E0A6D39ABED111A36000A0C99609CA2C2BA4@macertco-srv1.ma.certco.com>
+ o NO_FP_API ("Andrija Antonijevic" <TheAntony@bigfoot.com>)
+ 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
o Properly initialize the PRNG in the absence of /dev/random.
- o > NO_RSA (ejs@bfd.com)
- > ./Configure -DNO_IDEA -DNO_RC5 -DNO_RC4 -DNO_RC2 -DNO_RSA -DNO_ERR linux-elf
- > I tried for a whole day to do this and could not get it to work. Linux
- > machine, kernel 2.0.36 and 2.2.1, redhat 5.2 latest, gcc and egcs , no
- > go. I also noticed the even with -DNO_IDEA, _DNO_RC2, etc. the make
- > still goes into those subdirectories and 'makes'.
+ 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 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 Mats Nilsson <mats.nilsson@xware.se>:
- "Add reference counting to all substructures of X509 etc. For instance,
- X509_NAME lacks a reference counter, while EVP_PKEY has one. I'm
- making COM-wrappers for selected parts of SSLeay for a project of ours,
- and has found this inconsistency in copy semantics annoying."
-
+ o
projects / openssl.git / blobdiff