> > The Problem:
> >
> > What is the textual syntax of an ldap certificate supposed to be like?
>
> It's supposed to be a fixed version of rfc1488, which, as you pointed out,
> is missing some rather important fields. I submitted the certificate code
> last year when I was with BNR - it's the code BNR / Northern Telecom uses
> in their Entrust security product. The folks at U-Mich rolled it into the
> main distribution, but they had another group somewhere in Europe that also
> submitted rfc1488 certificate fixes. I think U-Mich tried to simply make a
> few minor changes in the code I submitted so that it matched the syntax
> being used by the other group, but it looks like they changed only the
> print routine and forgot the parse routine.
Just to confirm, this is indeed the case. We should've also fixed the
parse routine and will do so now. -- Tim