Add the corresponding AES parts while I'm at it.
make update

PR: 768
Submitted by: Vadim Fedukovich <vf@unity.net>

Submitted by: Douglas Stebila
Reviewed by: Bodo Moeller

(see X.520 aka ISO/IEC 9594-6)

Submitted by: Douglas Stebila <douglas.stebila@sun.com>

Submitted by: Vadim Fedukovich <vf@unity.net>
Reviewed by: Lutz Jaenicke
PR: 80

Submitted by: Michael Bell <michael.bell@rz.hu-berlin.de>
Reviewed by: Lutz Jaenicke
PR: 83

<michael.bell@rz.hu-berlin.de>).

Nils Larsch <nlarsch@compuserve.de>.

Submitted by: Nils Larsch

Submitted by: Nils Larsch <nla@trustcenter.de>

of feedback bits

RFCs concerning X.500 directories use UID as a shorter name for the
attribute type userId, which is defined by CCITT and available through
RFCs 1274 and 2247.

Unfortunately, if some applications have used the name "UID" for the
uniqueIdentifier attribute type, they will produce incorrect results.
However, I found it better to follow the standards that are out there
rather than having our own incompatible one.

Fix (?): Delete 'ip-pda 6' (id-pda-pseudonym) because it does not exist
in RFC 3039.

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

OpenBSD /dev/crypto (this will be revamped later when the appropriate machinery
is available).

abort with errors if no name is defined for some object, which was the
case for 'pilotAttributeType 27'.

Also avoid this very situation by assigning the name
'pilotAttributeType27'.

Note that all *_it variables are suddenly non-existant according to
libeay.num.  This is a bug that will be corrected.  Please be patient.

Add revelant new X509V3 extensions.

Add OIDs.

Fix ASN1 memory leak code to pop info if external allocation used.