- Made sure some changed behavior is documented in CHANGES.

[openssl.git] / STATUS

diff --git a/STATUS b/STATUS
index 8615b04e2457de2037134de0be3ae35899ed933b..7aa79674dd8dc66963cf9491f1b352be6884b06b 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,47 +1,34 @@
 
   OpenSSL STATUS                           Last modified at
 
   OpenSSL STATUS                           Last modified at

-  ______________                           $Date: 1999/04/29 21:51:00 $
+  ______________                           $Date: 1999/12/05 00:40:53 $

 
   DEVELOPMENT STATE
 
 
   DEVELOPMENT STATE
 

-    o  OpenSSL 0.9.3:  Under development...
-                       Proposed freeze  date: Mon May  8th, 1999
-                       Proposed release date: Mon May 17th, 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
 
     o  OpenSSL 0.9.2b: Released on March    22th, 1999
     o  OpenSSL 0.9.1c: Released on December 23th, 1998
 

-     [ Proposed new numbering scheme: <major>.<minor>[<patchlevel>]
-       0.9.1c is   0913
-       1.0    is 010000
-       1.0  a is 010001
-       1.8  z is 01081a ]
-

   RELEASE SHOWSTOPPERS
 
   RELEASE SHOWSTOPPERS
 

-    o Compilation warnings: ctype-related int vs. char
-    o BSD/OS: assembler functions must not have leading underscores
-    o exptest and rsa_oaep_test fail with irix64-*
-      (Don Badrak <dbadrak@geo.census.gov>: "Re: Problems to compile openssl
-         on IRIX 6.2", openssl-users)
-    o BN_add test fails on Caldera OpenLinux 1.3
-      (Marc Christensen <Marc.Christensen@m.cc.utah.edu>
-         "Compiles but fails big number test?", openssl-users)
- 

   AVAILABLE PATCHES
 
   AVAILABLE PATCHES
 

-    o OCSP (titchenert@certco.com) 
+    o shared libraries <behnke@trustcenter.de>

     o getenv in ca.c and x509_def.c (jaltman@watsun.cc.columbia.edu)
     o getenv in ca.c and x509_def.c (jaltman@watsun.cc.columbia.edu)

-    o linux dynamic libs (colin@field.medicine.adelaide.edu.au)
-    o MingW support (niklas@canit.se)
+    o SMIME tool (demo), Sampo Kellomaki <sampo@iki.fi>
+    o CA.pl patch (Damien Miller)
+    o FreeBSD 3.0 changes (Richard Levitte)

 
   IN PROGRESS
 
     o Steve is currently working on (in no particular order):
         Proper (or at least usable) certificate chain verification.
 
   IN PROGRESS
 
     o Steve is currently working on (in no particular order):
         Proper (or at least usable) certificate chain verification.

-        Documentation on X509 V3 extension code.
-        PKCS#12 code cleanup and enhancement.
-       PKCS #8 and PKCS#5 v2.0 support.

        Private key, certificate and CRL API and implementation.
        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 Mark is currently working on:
         Folding in any changes that are in the C2Net code base that were
 
     o Mark is currently working on:
         Folding in any changes that are in the C2Net code base that were


@@ -73,16 +60,16 @@
 
   NEEDS PATCH
 
 
   NEEDS PATCH
 

-    o  broken demos

     o  salzr@certco.com (Rich Salz): Bug in X509_name_print
        <29E0A6D39ABED111A36000A0C99609CA2C2BA4@macertco-srv1.ma.certco.com>
     o  salzr@certco.com (Rich Salz): Bug in X509_name_print
        <29E0A6D39ABED111A36000A0C99609CA2C2BA4@macertco-srv1.ma.certco.com>

-    o  Jean-Hugues ROYER <jhroyer@joher.com>: rsa_oaep.c with Watcom C

     o  $(PERL) in */Makefile.ssl
     o  "Sign the certificate?" - "n" creates empty certificate file
     o  $(PERL) in */Makefile.ssl
     o  "Sign the certificate?" - "n" creates empty certificate file

-    o  dubious declaration of crypt() in des.h

 
   OPEN ISSUES
 
 
   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
     o  The Makefile hierarchy and build mechanism is still not a round thing:
 
        1. The config vs. Configure scripts


@@ -103,6 +90,11 @@
                compiler PIC and linker DSO flags from Apache
                into the OpenSSL Configure script.
 
                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  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


@@ -136,17 +128,4 @@
 
   WISHES
 
 
   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