where the new functions are mentioned.

and add example of extension aliasing. Also fix
the extension aliasing because it didn't work :-)

-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline''.

This better reflects their behaviour.

Submitted by: Martin Kraemer <martin.kraemer@mch.sni.de>

((void *)0), by have a 0 instead.

Fix so CRLDistributionPoints relativeName option uses
the correct type.

represent everything by OIDs.

new purpose getting function.

Update the ca-cert.pem and pca-cert.pem "CA" certificates so they
really are CA certificate: that is they have the appropriate extensions.

either and has a static and dynamic mix.

yet.

Add a function X509_STORE_CTX_purpose_inherit() which implements the logic
of "inheriting" purpose and trust from a parent structure and using a default:
this will be used in the SSL code and possibly future S/MIME.

Partial documentation of the 'verify' utility. Still need to document how all
the extension checking works and the various error messages.

trust settings of the root CA.

After a few fixes it seems to work OK.

Still need to add support to SSL and S/MIME code though.

Extend the X509_PURPOSE structure to include shortnames for purposed and default
trust ids.

Still need some extendable trust checking code and integration with the SSL and
S/MIME code.

Fix so EVP_PKEY_rset_*() check return codes.

certificate: currently this includes trust settings
and a "friendly name".

Submitted by: Lennart Bång, Bodo Möller

tolerated in certificates.

ultimately lead to certificate chain verification. It is
VERY EXPERIMENTAL at present though.

Fix a bug in the X509_get_d2i() functions which didn't check if crit was NULL.

config file (change RAW to DER).

Hint from: Andrija Antonijevic <TheAntony2@bigfoot.com>

zone number.

documentation to reflect the STACK_OF(CONF_VALUE) change to the CONF lib and
use ANSI typedefs for X509V3_EXT_I2D and X509V3_EXT_FREE.

seemed like a good idea at the time... several hours later it was rather
obvious that these are used all over the place making the changes rather
extensive.

to use 'void *' rather than 'char *' for an "arbitrary extension".

in cryptlib.h (which is often included as "../cryptlib.h"), then the
question remains relative to which directory this is to be interpreted.
gcc went one further directory up, as intended; but makedepend thinks
differently, and so probably do some C compilers.  So the ../ must go away;
thus e_os.h goes back into include/openssl (but I now use
#include "openssl/e_os.h" instead of <openssl/e_os.h> to make the point) --
and we have another huge bunch of dependency changes.  Argh.