diff options
| author | Ronnie Sahlberg <ronnie_sahlberg@ozemail.com.au> | 2012-05-28 09:40:54 +0000 |
|---|---|---|
| committer | Ronnie Sahlberg <ronnie_sahlberg@ozemail.com.au> | 2012-05-28 09:40:54 +0000 |
| commit | 4baba1c6845549f75a9cd8480914b6b2bc3da5cd (patch) | |
| tree | 4a227ff601095b506e50b8a263ebe16e055d5a9c /asn1/ldap | |
| parent | ee57847596ca14d02588b5690a3a59cb8296fdd4 (diff) | |
| download | wireshark-4baba1c6845549f75a9cd8480914b6b2bc3da5cd.tar.gz | |
Sometimes you might have plaintext LDAP for a SASL LDAP connection if the handshake never occured.
Observed with exchange in some configurations.
From Matthieu Patou <mat@matws.net>
svn path=/trunk/; revision=42875
Diffstat (limited to 'asn1/ldap')
| -rw-r--r-- | asn1/ldap/packet-ldap-template.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/asn1/ldap/packet-ldap-template.c b/asn1/ldap/packet-ldap-template.c index b0c49f4959..ce9e514e26 100644 --- a/asn1/ldap/packet-ldap-template.c +++ b/asn1/ldap/packet-ldap-template.c @@ -1922,6 +1922,12 @@ this_was_not_normal_ldap: /* we are done */ return; } + /* Ok it might be a strange case of SASL still + * It has been seen with Exchange setup to MS AD + * when Exchange pretend that there is SASL but in fact data are still + * in clear*/ + if ((sasl_len + 4) == tvb_length_remaining(tvb, 0)) + tcp_dissect_pdus(tvb, pinfo, tree, ldap_desegment, 4, get_sasl_ldap_pdu_len, dissect_sasl_ldap_pdu); end: return; } |