Furthermore, it create conflicts with LDAP and some RFCs that define
"UID" as a lable for the attribute type userId (which we haven't even
defined here).

The next question is if we should update objects.txt with the added
stuff from the main trunk.

main documentation, so let's warn them a little more, so the word
"OBSOLETE" really gets understood.

Fix: Some ip-pda OIDs were incorrect (cf. RFC 3039).

Also change Perl scripts to put auto-generation warning in the
first lines of the file.

Submitted by: Richard Shapiro <rshapiro@abinitio.com>

Submitted by: Richard Shapiro <rshapiro@abinitio.com>

'OpenSSL_0_9_6-stable'.

Submitted by: Richard Shapiro <rshapiro@abinitio.com>

released.

essentially overwrites itself with the new ENGINE, with the exception of
reference counts, ex_data structures, and other 'admin' elements. However
if the new ENGINE doesn't populate certain elements, there's the risk of
the "dynamic" ENGINE's elements showing through - the "cmd_defns" were just
one of the possibilities. This implements a more comprehensive cleanup.

device. This change enables it for building as a self-contained "dynamic"
ENGINE, to help testing such mechanisms.

object - otherwise we overwrite any flags that had been previously set in
the DSO before calling DSO_load().

Extentions of the explanations to the linking problem on Win32.  Provided by Andrew Gray <agray@iconsinc.com>

Extentions of the explanations to the linking problem on Win32.  Provided by Andrew Gray <agray@iconsinc.com>

(shinagawa@star.zko.dec.com).

(shinagawa@star.zko.dec.com).

 to trust that norm.  I might implement a control for this later on

 to trust that norm.  I might implement a control for this later on

elliptic curves are are relatively faster than on PCs anyway)

On VAX, all global variables are accessed through functions, so skip
doing transfer entries for variables.

Forgot the looping gotos.

directory, trust the building scripts to handle it properly.

And this finishes this engine, it now offers all ciphers and digests
that RSAref 2.0 has.

Restructure the code and comment it a bit.
Prepare for the presence of digests.

instead.  This also makes it possible for users to simply give said
shareable library as argument for the -engine option.