Donn Cave wrote:
> In article <453D95EA.1020602 at animats.com>,
> John Nagle <nagle at animats.com> wrote:
>>>>Note that
>>>> "OU=Terms of use at www.verisign.com/rpa (c)00"
>>>>with a "/" in the middle of the value field.
>> ...
>>>Is there a workaround for this? Without rebuilding Python
>>and becoming incompatible?
>> As a practical matter, I think it's fairly safe to assume
> there will be no values that include / in a context like
> really looks like that X.500 style distinguished name.
>> So if you parse out that string in those terms, and require
> each of those key = value pairs to have reasonable values -
> key has no embedded spaces, value has non-zero length - then
> you should be OK. Re-join any invalid component to its
> predecessor's value.
Don't make such assumptions when parsing DNs!
It's a major PITA in the long run.
Ciao, Michael.
