Reflect correct filename

[openssl.git] / STATUS

diff --git a/STATUS b/STATUS
index e7b7687272249d92f54a07fd480fd7883f63f6e9..0a1a99428ffa28e0ee597052a3cda1d5a5b22770 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,6 +1,6 @@
 
   OpenSSL STATUS                           Last modified at
-  ______________                           $Date: 1999/01/21 13:01:20 $
+  ______________                           $Date: 1999/01/30 17:34:59 $
 
   DEVELOPMENT STATE
 
@@ -13,7 +13,13 @@
 
   IN PROGRESS
 
-    o  Ben is folding in his patches
+    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.
 
   NEEDS PATCH
 
@@ -30,19 +36,7 @@
                       itself. Then we can avoid a lot of those platform checks
                       which are currently in Configure.
 
-       2. The massive symlinking of Makefile.ssl -> Makefile:
-          First the `make -f Makefile.ssl links' command is nasty, second the
-          whole process is slow and third it seems to be done without real
-          need. And forth, the dependecies are currently missing.  And fifth,
-          it's complicated to always go to the top-level in order to get the
-          local variables overriden.
-          Suggestion: Rename Makefile.ssl to Makefile.in, add
-                      dependencies to Makefile.in and change the build process
-                      to _generate_ Makefile out of Makefile.in by
-                      substituting variables like CC, etc. This solves the
-                      above problems.
-
-       3. The xxx.org -> xxx.h generation:
+       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
@@ -89,19 +83,15 @@
                to date.
                Paul +1
 
-    o  Ralf has ported Stephen's pkcs12 program to OpenSSL (the 
-       ASN.1 stuff Eric recently changed :-( ), but needs some help from
-       Stephen at two source locations.  Stephen itself also has ported his
-       internal pkcs12 0.53 version to OpenSSL, but thinks we still shouldn't
-       incorporate it into OpenSSL because it needs more cleanups. Ralf still
-       thinks pkcs12 should be incorporated better now than later because it's
-       nasty to not have it in the core - one always has to install it
-       manually and a lot of people use it. So, should we incorporate it?
-       BTW, we have to be carefully because of the pkcs12 license: There are
-       some things which don't match the OpenSSL license, so Stephen has to
-       change it for us when we want to incorporate the code.
-
-       Status: Ralf +1, Stephen -0
+    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