The branch, v3-4-test has been updated
via 8c2493f s3: Make winbind recover from a signing error
from e18ef6c s3: Stop using the write cache after an oplock break
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-4-test
- Log -----------------------------------------------------------------
commit 8c2493ff2e646928035ec7296f4451f09390f6aa
Author: Volker Lendecke <[email protected]>
Date: Wed Nov 17 08:56:28 2010 -0700
s3: Make winbind recover from a signing error
When winbind sees a signing error on the smb connection to a DC (for
whatever
reason, our bug, network glitch, etc) it should recover properly. The "old"
code in clientgen.c just closed the socket in this case. This is the right
thing to do, this connection is spoiled anyway. The new, async code did not
do
this so far, which led to the code in winbindd_cm.c not detect that we need
to
reconnect.
Fix bug #7800 (winbind does not recover from smb signing errors).
-----------------------------------------------------------------------
Summary of changes:
source3/libsmb/async_smb.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source3/libsmb/async_smb.c b/source3/libsmb/async_smb.c
index e683e37..0336ff2 100644
--- a/source3/libsmb/async_smb.c
+++ b/source3/libsmb/async_smb.c
@@ -848,6 +848,8 @@ static NTSTATUS validate_smb_crypto(struct cli_state *cli,
char *pdu)
if (!cli_check_sign_mac(cli, pdu)) {
DEBUG(10, ("cli_check_sign_mac failed\n"));
+ close(cli->fd);
+ cli->fd = -1;
return NT_STATUS_ACCESS_DENIED;
}
--
Samba Shared Repository
