summaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2006-02-12 16:44:30 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 11:10:05 -0500
commitd672d8fd6bd2957f6177c809c77b3d2c1a2fddca (patch)
tree2499601e9b85aae56cdb4b996f9ef125d0e0a048 /MAINTAINERS
parent75ef18fa7510d894ccc4540d82616110c3166db3 (diff)
downloadsamba-d672d8fd6bd2957f6177c809c77b3d2c1a2fddca.tar.gz
samba-d672d8fd6bd2957f6177c809c77b3d2c1a2fddca.tar.bz2
samba-d672d8fd6bd2957f6177c809c77b3d2c1a2fddca.zip
r13473: Back port r13470, r13471, r13472 from Samba4. Thanks Andrew:
----------------------------------- Thanks to a report from VL: We were causing mayhem by weakening the keys at the wrong point in time. I think this is the correct place to do it. The session key for SMB signing, and the 'smb session key' (used for encrypting password sets) is never weakened. The session key used for bulk data encryption/signing is weakened. This also makes more sense, when we look at the NTLM2 code. Andrew Bartlett ----------------------------------- With more 'try all options' testing, I found this 'simple' but in the NTLM2 signing code. Andrew Bartlett ----------------------------------- After Volker's advise, try every combination of parameters. This isn't every parameter on NTLMSSP, but it is most of the important ones. This showed up that we had the '128bit && LM_KEY' case messed up. This isn't supported, so we must look instead at the 56 bit flag. Andrew Bartlett ----------------------------------- We should now try retesting with NT4. This should be standalone enough to port into a SAMBA_3_0_RELEASE branch fix. Jeremy. (This used to be commit b9b8cd1752aeab049983c1a6038edf2231ec10a4)
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions