summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/security/forcedirectorysecuritymode.xml
diff options
context:
space:
mode:
authorGerald Carter <jerry@samba.org>2003-07-31 19:01:22 +0000
committerGerald Carter <jerry@samba.org>2003-07-31 19:01:22 +0000
commit0da36b22ff3382f2e4a86f4090ad8097a2dd8a32 (patch)
treebb332db7a3aad230b5eb8779ee3336ed42016074 /docs/docbook/smbdotconf/security/forcedirectorysecuritymode.xml
parentf86708be990b237b2196b91bd99b88e946b42c40 (diff)
downloadsamba-0da36b22ff3382f2e4a86f4090ad8097a2dd8a32.tar.gz
samba-0da36b22ff3382f2e4a86f4090ad8097a2dd8a32.tar.bz2
samba-0da36b22ff3382f2e4a86f4090ad8097a2dd8a32.zip
only honor the first OID in the sessetup snego negotiate. Deviates
from RFC but I'm smelling a client bug here. /* only look at the first OID for determining the mechToken -- accoirding to RFC2478, we should choose the one we want and renegotiate, but i smell a client bug here.. Problem observed when connecting to a member (samba box) of an AD domain as a user in a Samba domain. Samba member server sent back krb5/mskrb5/ntlmssp as mechtypes, but the client (2ksp3) replied with ntlmssp/mskrb5/krb5 and an NTLMSSP mechtoken. --jerry */ (This used to be commit 731420b03dbc15977822f74047e931dc62284fc0)
Diffstat (limited to 'docs/docbook/smbdotconf/security/forcedirectorysecuritymode.xml')
0 files changed, 0 insertions, 0 deletions