X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=STATUS;h=ca0d94fc1d4bbc8f96f747e1c917e5c6256343b6;hb=cba5068d1047fd8326a090d41f259513edb70e1b;hp=e7b7687272249d92f54a07fd480fd7883f63f6e9;hpb=69d1dfba24c9200a2cd307bf0b1949f6bb6291ea;p=oweals%2Fopenssl.git diff --git a/STATUS b/STATUS index e7b7687272..ca0d94fc1d 100644 --- a/STATUS +++ b/STATUS @@ -1,19 +1,57 @@ OpenSSL STATUS Last modified at - ______________ $Date: 1999/01/21 13:01:20 $ + ______________ $Date: 1999/02/28 20:51:38 $ DEVELOPMENT STATE - o OpenSSL 0.9.2: Under development. + 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 RELEASE SHOWSTOPPERS AVAILABLE PATCHES + o Solaris AS error (kenji@miyake.org) + 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) + 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. + + 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 Ben is currently working on: + 1. Function Prototype Thought Police issues. + 2. Integrated documentation. + 3. New TLS Ciphersuites. + 4. Anything else that takes his fancy. NEEDS PATCH @@ -30,23 +68,13 @@ 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 + 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 @@ -89,19 +117,24 @@ 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). + + 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'. WISHES @@ -113,3 +146,9 @@ SSLeay-0.9.1b RPM already includes some patches which do some of this. I can forward them if you wish." + o Mats Nilsson : + "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." +