RE: userCertificate;binary NOT ASCII

[Rob De Langhe <rob.delanghe@telindus.be>]

Yep, I can confirm, I have exactly the same behaviour, which kept me busy
for a few days trying to figure out what I did wrong (if anything) until I
found that I had /usr/bin in my PATH before /usr/local/bin.
/usr/bin/ldapsearch is the Solaris(8 & 9)-shipped version, which prints
'binary=NOT ASCII', and /usr/local/bin/ldapsearch is the OpenLDAP version,
which prints the value as a whole.

I am curious why ...

Rob

-----Original Message-----
From: Armin Wenz [mailto:awenz@mtgnet.de]
Sent: vrijdag 7 maart 2003 08:08
To: openldap-software@OpenLDAP.org
Subject: userCertificate;binary NOT ASCII


When using OL 2.0.27 I got different behaviours for 
ldapmodify/ldapsearch on Linux/Solaris 2.6 and Solaris 8.
When searching for userCertificate in the first case I got
userCertificate;binary:: MIIECTCCAv<encoded data>
On the Solaris 8 machine it's
userCertificate;binary=NOT ASCII

Some with ldapadd/modify
On Linux/S2.6 I can do
userCertificate;binary::  <file://....
On Solaris 8 this is not recognized.

Same with all other binary data like CaCertificate and CRL.

Can anybody explain this?

-- 

Armin Wenz