At 11:42 14.11.2002 +1300, you wrote:
On Wed, Nov 13, 2002 at 09:35:47AM +0100, Karl-Michael Werzowa wrote:
> letters, etc. (If you use an Ö or Ä it may be easy, but what about
> hungarian, slovak, croatian characters? How to type these? Do you know the
> possible transcripts?)
> The best way seems to be to have an ascii transcript and the full BMPString
> in LDAP and certificates.
Don't get me started! :-)
As it is, we're talking about Microsoft Active Directory LDAP here - so I
need to find out just what that is from a charset point of view. I mean, M$
make a big thing over Unicode - but the LDAP data certainly isn't Unicode.
In fact, from what I can find off Google, LDAP (include AD) uses ISO-10646 -
which is a superset of Unicode. Apparently all standard ASCII chars stay the
same, and the rest are converted into the double-byte Unicode. However, I'm
definitely getting ASCII-8bit chars out of LDAP - so I don't know what the
hell's going on :-)
--
Cheers
Jason Haar
LDAP normally uses UTF-8, which is a way to encode iso-10646
characters. 7bit ascii looks the same in utf-8 and ascii, but higher up the
charset the encoding takes 2 (in case of a simple Ö) to 6 characters.
And that works. I have a CA with an ö in its name, and I can
fetch its CRL from LDAP without problems.
One hint: Your LDAP server might behave differently depending on
the client's version number. Do you use version 3?
See RFC2553.
Jörn
(Guess why there is an ö in my CA certificate)
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
