The 6th draft of X.509 2000 (which was all I had handy) has the following
to say about the encoding of SETs OF:
<quote>
In order to enable the validation of SIGNED and SIGNATURE types in a
distributed environment, a distinguished encoding is required. A
distinguished encoding of a SIGNED or SIGNATURE data value shall be
obtained by applying the Basic Encoding Rules defined in ITU-T Rec. X.690
(1997) | ISO/IEC 8825 :1998, with the following restrictions:
[...]
e) the components of a Set-of type shall be encoded in ascending order of
their octet value;
[...]
</quote>
//oscar
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Stroder
> Sent: den 26 september 2000 14:45
> To: [EMAIL PROTECTED]
> Subject: Re: OCSP and issuerNameHash (was: Object names)
>
> I'm currently in the process of writing a Python class for X.500
> names. And for several reasons doing proper comparison of X.500
> names is pretty complex. Multi-attribute RDNs are one of the
> reasons.
smime.p7s
