On 10/3/06 5:36, Adrian De los Santos <[EMAIL PROTECTED]> wrote: > > On Mar 10, 2006, at 11:30 AM, Adrian De los Santos wrote: > >> >> On Mar 10, 2006, at 11:28 AM, Chris Ridd wrote: >> >>> On 10/3/06 5:22, Adrian De los Santos <[EMAIL PROTECTED]> wrote: >>> >>>> On Mar 9, 2006, at 6:28 PM, Graham Barr wrote: >>>> >>>>> >>>>> Has anything changed in your perl installation ? >>>>> >>>>> What versions of Net::LDAP and Convert::ASN1 do you have >>>>> installed ? >>>>> >>>>> I suspect the decoding actually got messed up before the bit you >>>>> pasted into you message. That is a big packet to have an offset of >>>>> 0xF800 >>>>> >>>>> >>>>> Graham. >>>>> >>>> >>>> No that im aware of, well, in fact i just updated Convert::ASN1 >>>> yesterday via cpan but i keep getting the same errors. I also tried >>>> to get the most recent Net::LDAP but according to cpan it was up to >>>> date. >>>> >>>> Here are the versions of Net::LDAP and Convert::ASN1 and Perl >>>> >>>> Net::LDAP -- 0.33 >>>> Convert::ASN1 -- 0.20 >>>> This is perl, v5.8.5 built for i386-linux-thread-multi >>>> >>>> Thanks a lot for your help. >>> >>> Is it possible to get a raw dump of the BER that the server's >>> returning? It >>> either looks like the server's sending something illegal back that's >>> confusing us, or we're incorrectly handling something. Rather hard >>> to say >>> though... >>> >> >> And.. how i get that raw dump ? >> >> Thanks and sorry for my ignorance on this matter.
(Adrian sent me the debug output direct.) It looks quite like the server was sending mangled BER. The LDAP result was actually very large (so the byte offsets logged were OK), but the server suddenly decided to send a PrintableString value instead of an OCTET STRING value, and it got even more confused from there on... Cheers, Chris
