the main library, but only with printing at present. To see this try:
openssl x509 -in cert.pem -text
on a certificate with some extensions in it.

GeneralizedTime.

of 'make errors' without causing huge re-organisations of files when a new
code is added.

Contributed by: Ulf Möller <ulf@fitug.de>

Contributed by: Anonymous <nobody@replay.com>

Submitted by: Neil Costigan <neil.costigan@celocom.com>
PR:

1.2.3.4 . Also added new function OBJ_txt2obj().

auto generated but not auto updated so it is included. Also remove the
encryption from the sample DSA keys.

Contributed by: Anonymous <nobody@replay.com>

Contributed by: Bodo Moeller <3moeller@informatik.uni-hamburg.de>

soon - I intend to do a lot of it!).

DSA_free(): this was causing crashes when for example an attempt was made
to handle a (currently) unsupported DH public key. Also X509_PUBKEY_set()i
wasn't checking errors from d2i_PublicKey().

Submitted by: Arne Ansper <arne@ats.cyber.ee>

Submitted by: Arne Ansper <arne@ats.cyber.ee>

in X509_STORE_new(), but document the fact that this variable is still
unused in the certificate verification process.

handling to x509.c

`openssl' and second, the shortcut symlinks for the `openssl <command>' are no
longer created. This way we have a single and consistent command line
interface `openssl <command>', similar to `cvs <command>'.

Notice, the openssl.cnf, openssl.c and progs.pl files were changed after a
repository copy, i.e. they still contain the complete file history.

zero unused bits.

(including if user presses ^C)

1. The already released version was 0.9.1c and not 0.9.1b

2. The next release should be 0.9.2 and not 0.9.1d, because
   first the changes are already too large, second we should avoid any more
   0.9.1x confusions and third, the Apache version semantics of
   VERSION.REVISION.PATCHLEVEL for the version string is reasonable (and here
   .2 is already just a patchlevel and not major change).
tVS: ----------------------------------------------------------------------