- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-Developers-Guide/unix-smb.xml
r746 r988 113 113 114 114 <para> 115 ManySMB clients uppercase passwords before sending them. I have no115 When plaintext passwords are used, very old SMB clients uppercase passwords before sending them. I have no 116 116 idea why they do this. Interestingly WfWg uppercases the password only 117 117 if the server is running a protocol greater than COREPLUS, so … … 124 124 </para> 125 125 126 <para> 127 Samba can try to cope with this by either using the "password level" 128 option which causes Samba to try the offered password with up to the 129 specified number of case changes, or by using the "password server" 130 option which allows Samba to do its validation via another machine 131 (typically a WinNT server). 126 <para>Samba will try an additional all lower cased password 127 authentication if it receives an all uppercase password. Samba used to 128 support an option called "password level" that would try to crack 129 password by trying all case permutations, but that option has been 130 removed. 132 131 </para> 133 132 … … 208 207 directory or a shared memory implementation. The lock file method 209 208 is clumsy and consumes processing and file resources, 210 the shared memory implementation is vastly prefer ed and is turned on209 the shared memory implementation is vastly preferred and is turned on 211 210 by default for those systems that support it. 212 211 </para>
Note:
See TracChangeset
for help on using the changeset viewer.