[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: x500UniqueIdentifier

To: Howard Chu <hyc@symas.com>
Subject: Re: x500UniqueIdentifier
From: Michael Ströder <michael@stroeder.com>
Date: Thu, 09 Dec 2010 18:56:18 +0100
Cc: Juan Gonzalez <jgcardoso@seguridata.com>, openldap-technical@openldap.org
In-reply-to: <4CFFFC6C.1010707@symas.com>
References: <801F0AF0A50D1F48A1E4DA25881C1CB401A22B9D@exch-bck> <4CFFC906.4080501@symas.com> <4CFFFC6C.1010707@symas.com>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101123 Lightning/1.0b1 SeaMonkey/2.0.11

Howard Chu wrote:
> I should also warn you, x500UniqueIdentifier has a bitstring syntax, and
> this syntax is extremely clumsy in LDAP. Judging from the certificate
> you sent me, you're trying to use this attribute as a regular
> octetstring. The two are quite different.

I suspected something like this. There has quite some confusion about
x500UniqueIdentifier also in other software:

https://issues.apache.org/bugzilla/show_bug.cgi?id=45107

Ciao, Michael.

References:
- x500UniqueIdentifier
  - From: "Juan Gonzalez" <jgcardoso@seguridata.com>
- Re: x500UniqueIdentifier
  - From: Howard Chu <hyc@symas.com>
- Re: x500UniqueIdentifier
  - From: Howard Chu <hyc@symas.com>

Prev by Date: Re: "slapadd: corrupted double-linked list"
Next by Date: openldap and kerberos integration
Index(es):
- Chronological
- Thread