http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=22948
User: sahlberg
Date: 2007/09/25 07:47 AM
Log:
not all SASL protected blobs use a GSS wrapper for the payload so we
cant check that the payload starts with BER tag 0x60 and an oid.
instead check that the length byte (first 4 bytes) look sane and if
SASL authentication has been negotiated on the connection
also, sometimes clients will mix both non-SASL and SASL protected LDAP
traffic on the same tcp connection by initially performing simple
unauthenticated searches on the database before performing the Bind.
Directory: /trunk/epan/dissectors/
Changes Path Action
+24 -21 packet-ldap.c Modified
Directory: /trunk/asn1/ldap/
Changes Path Action
+21 -18 packet-ldap-template.c Modified