| commit | a78ec00991e4516106f50cc1616cf1467cc085e6 | |
| author | Stefan Metzmacher <metze@samba.org> | |
| Thu, 17 Jul 2014 12:20:58 +0000 (17 14:20 +0200) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Thu, 7 Aug 2014 14:43:09 +0000 (7 16:43 +0200) | ||
| tree | 5b6f06dfec1dd87fa11e019ae6982cba0feb0fef | treesnapshot (tar.gz zip) |
| parent | 8907f5e06977c6981f5484f5c054102d4aab44f7 | commitdiff |
s4:rpc_server/netlogon: keep a global challenge table
Some clients call netr_ServerReqChallenge() and netr_ServerAuthenticate3()
on different connections. This works against Windows DCs as they
have a global challenge table.
A VMware provisioning task for Windows VMs seemy to rely on this behavior.
As a fallback we're storing the challenge in a global memcache with a fixed
size. This should allow these strange clients to work against a
Samba AD DC.
Bug: https://bugzilla.samba.org/show_bug.cgi?id=10723
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
(similar to commit 321ebc99b5a00f82265aee741a48aa84b214d6e8)
Some clients call netr_ServerReqChallenge() and netr_ServerAuthenticate3()
on different connections. This works against Windows DCs as they
have a global challenge table.
A VMware provisioning task for Windows VMs seemy to rely on this behavior.
As a fallback we're storing the challenge in a global memcache with a fixed
size. This should allow these strange clients to work against a
Samba AD DC.
Bug: https://bugzilla.samba.org/show_bug.cgi?id=10723
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
(similar to commit 321ebc99b5a00f82265aee741a48aa84b214d6e8)
| source4/rpc_server/netlogon/dcerpc_netlogon.c | diffblobblamehistory |