From: Chris R. <chr...@me...> - 2002-06-05 08:00:58
|
On 4/6/02 11:08 pm, ma...@mj... <ma...@mj...> wrote: > It looks like the attribute is binary: >=20 > changes:: >>=20 > b2JqZWN0Y2xhc3M6dG9wCm9iamVjdGNsYXNzOm9yY2xOZXRBZ > GRyZXNzCmNuOkFERFJF >>=20 >=20 > Note the double ":", which in LDIF normally connotates that the > value is binary.=20 >=20 > Try doing a base64 decode on the value and see what you get. >=20 > Mark This looks like the same problem someone else (Czachary) at Wiley was getting! The LDIF writer will encode any values for output in base64 if the= y contain unsafe characters which would confuse LDIF readers. Things like carriage-returns, and so on. If you decode the value it looks like it contains bits of an entry. It coul= d be random junk that the server's returning, or it could be that Net::LDAP's putting some junk data in there... DB<1> x $bin 0 =20 "objectclass:top\cJobjectclass:orclNetAddressList\cJcn:ADDRESS_LIST_0\cJorc= l version:v0.0\cJorclnetaddrlist:000:cn=3DADT?T?=97cB???e?]\c\?cX\\?Y\cN?????e?]\= e \e?\cX?[\cX[???\cS????cY?Y\cN?\cC#c??\cCscS3c\cC33C3?cC\cCS?\cSc?s#C?P?7&V\= c WF?\cV??6?&6?cVF????W'6?V??6?&6?cVF??&V\cWFWF??7F\cV?cC=A3#\cC\cC#\cCS#?\cSsS= \ cS\cS\cG=A0??F?g?F??7F\cV?cC=A3#\cC\cC#\cCS#?\cSsS\cS\cS\cG=A0=A0" Can you turn up logging in Net::LDAP (create the Net::LDAP object with the debug parameter set to 3), repeat the exact query and send us the hex output? Cheers, Chris |