X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=STATUS;h=d68ab036c154fffee904838927a56d2017857dcb;hp=5cf8ef47d90d6c44d219ba712d6f957eaac50e9e;hb=f3c751067a696e0774a56800caa5a8793f0a608d;hpb=6ccec4393389c9a825010a2ceb561218ecb1da7a diff --git a/STATUS b/STATUS index 5cf8ef47d9..d68ab036c1 100644 --- a/STATUS +++ b/STATUS @@ -1,33 +1,79 @@ OpenSSL STATUS Last modified at - ______________ $Date: 1999/02/01 08:18:31 $ + ______________ $Date: 1999/05/20 01:42:57 $ DEVELOPMENT STATE - o OpenSSL 0.9.2: Under development. + o OpenSSL 0.9.3: Freezed... only bugfixes and cleanups allowed! + Proposed release date: Mon May 24th, 1999 + Release manager: Ben Laurie + !! Important: Any non-bugfix, non-cleanup + !! and non-documentation commits should + !! be approved by Ben, first. + + o OpenSSL 0.9.2b: Released on March 22th, 1999 o OpenSSL 0.9.1c: Released on December 23th, 1998 RELEASE SHOWSTOPPERS + o BSD/OS: assembler functions must not have leading underscores + AVAILABLE PATCHES + o OCSP (titchenert@certco.com) + o getenv in ca.c and x509_def.c (jaltman@watsun.cc.columbia.edu) + 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. + Documentation on X509 V3 extension code. + PKCS #8 and PKCS#5 v2.0 support. + Private key, certificate and CRL API and implementation. + Checking and bugfixing PKCS#7 (S/MIME code). 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. + => It still dumps core, so I suspend this and investigate + again for OpenSSL 0.9.3. + 2. The perl/ stuff to make it really work the first time ;-) + => I'll investigate a few more hours for OpenSSL 0.9.2 + 3. The new documentation set in POD format under doc/ + => I'll investigate a few more hours for OpenSSL 0.9.2 + 4. More cleanups to get rid of obsolete/old/ugly files in the + source tree which are not really needed. + => Done all which were possible with my personal knowledge + + 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 + o broken demos + o salzr@certco.com (Rich Salz): Bug in X509_name_print + <29E0A6D39ABED111A36000A0C99609CA2C2BA4@macertco-srv1.ma.certco.com> + o [ Compilation warnings: ctype-related int vs. char ] + => now casts (unsigned char), maybe those arrays should have + members of that type rather than plain char (i.e. + unsigned char *p; ....; if (isspace(*p)) ...; where it's now + char *p; ....; if (isspace((unsigned char)*p)) ...;) + o $(PERL) in */Makefile.ssl + o "Sign the certificate?" - "n" creates empty certificate file + o dubious declaration of crypt() in des.h + OPEN ISSUES o The Makefile hierarchy and build mechanism is still not a round thing: @@ -41,31 +87,6 @@ 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 @@ -100,13 +121,17 @@ 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 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 : + "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."