Tuesday, August 24, 2004, 11:33:16 PM, Chris wrote:
Chris> I went to
Chris> http://www.opinionatedgeek.com/dotnet/tools/Base64Decode/Default.aspx
Chris> and entered the "gibberish" and it decoded into readable text.
Chris> Therefore, The Bat! is encoding those addresses in base64 for some
Chris> reason.
Chris, thanks for this hint. I started thinking that the only reason
for a Base64Encode was a strange character in the street address. The
three addresses that produced the encoding in the LDIF file all had a
carriage return and linefeed in them or a newline (not sure which).
The two shorter ones at the end of the street address and the longer
one in the middle.
So it seems that TheBat! LDIF files use Base64Encode when a
non-alphanumeric is in the data. FireFox can import and decode the
Base64Encode. But when Firefox exports the file again as LDIF it does
it as two lines, homePostalAddress: and mozillaHomePostalAddress2:
instead of Base64Encode.
All along I assumed LDIF was simple and equal across systems and
applications. Boy was I wrong! It can be converted but its full of
ifs, buts, whatevers, and quirks. :-( :-) Like tragic and comedy
theatre masks.
--
Regards,
Plan9
"It is all right to decorate construction
but never construct decoration" --Pugin
________________________________________________
Current version is 2.12.00 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
