summaryrefslogtreecommitdiff
path: root/docs/docbook/faq/features.sgml
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2003-02-01 13:01:31 +0000
committerAndrew Bartlett <abartlet@samba.org>2003-02-01 13:01:31 +0000
commit2f5d3e7a64a7f756aa289294050e57b34c6dfb17 (patch)
treecea08d868eaff30268c4b907493e2673a0c2e703 /docs/docbook/faq/features.sgml
parent4e8a08592340b2bd13369a205f0a30b9e827f997 (diff)
downloadsamba-2f5d3e7a64a7f756aa289294050e57b34c6dfb17.tar.gz
samba-2f5d3e7a64a7f756aa289294050e57b34c6dfb17.tar.bz2
samba-2f5d3e7a64a7f756aa289294050e57b34c6dfb17.zip
We now have client-side SMB signing support!
This checking allows us to connect to Microsoft servers the use SMB signing, within a few restrictions: - I've not get the NTLMSSP stuff going - it appears to work, but if you break the sig - say by writing a zero in it - it still passes... - We don't currently verfiy the server's reply - It works against one of my test servers, but not the other... However, it provides an excellent basis to work from. Enable it with 'client signing' in your smb.conf. Doc to come (tomorrow) and this is not for 3.0, till we get it complete. The CIFS Spec is misleading - the session key (for NTLMv1 at least) is the standard session key, ie MD4(NT#). Thanks to jra for the early work on this. Andrew Bartlett (This used to be commit 1a2738937e3d80b378bd0ed33cd8d395fba2d3c3)
Diffstat (limited to 'docs/docbook/faq/features.sgml')
0 files changed, 0 insertions, 0 deletions