tldap: Receiving "msgid == 0" means the connection is dead
authorVolker Lendecke <vl@samba.org>
Tue, 11 Aug 2020 16:09:14 +0000 (18:09 +0200)
committerVolker Lendecke <vl@samba.org>
Fri, 21 Aug 2020 20:37:24 +0000 (20:37 +0000)
commitccaf661f7c75717341140e3fbfb2a48f96ea952c
tree70d62242aca1fac8cb4398bf5c9a32e92f1e2cf7
parenta4ecd112e7754ab25bcae749594952a28c4c8905
tldap: Receiving "msgid == 0" means the connection is dead

We never use msgid=0, see tldap_next_msgid(). RFC4511 section 4.4.1
says that the unsolicited disconnect response uses msgid 0. We don't
parse this message, which supposedly is an extended response: Windows
up to 2019 sends an extended response in an ASN.1 encoding that does
not match RFC4511.

Bug: https://bugzilla.samba.org/show_bug.cgi?id=14465

Signed-off-by: Volker Lendecke <vl@samba.org>
Reviewed-by: Stefan Metzmacher <metze@samba.org>
Autobuild-User(master): Volker Lendecke <vl@samba.org>
Autobuild-Date(master): Fri Aug 21 20:37:25 UTC 2020 on sn-devel-184
selftest/knownfail.d/ticket_expiry [deleted file]
source3/lib/tldap.c