summaryrefslogtreecommitdiff
path: root/docs/textdocs
diff options
context:
space:
mode:
authorSamba Release Account <samba-bugs@samba.org>1996-06-19 13:23:46 +0000
committerSamba Release Account <samba-bugs@samba.org>1996-06-19 13:23:46 +0000
commit851ee418b499df481b765286405cd761e91dcaaf (patch)
treec44bf5a4bc6f4f5adf38e39ea29d6abe778f40c4 /docs/textdocs
parentddc4fc68b97f376b97c3a59febf241ace3fb8fc7 (diff)
downloadsamba-851ee418b499df481b765286405cd761e91dcaaf.tar.gz
samba-851ee418b499df481b765286405cd761e91dcaaf.tar.bz2
samba-851ee418b499df481b765286405cd761e91dcaaf.zip
Basic doc changes to keep up to date.
Dan (This used to be commit 6d81d56f929e763bcf6b1f7a61aabaf884c4aad4)
Diffstat (limited to 'docs/textdocs')
-rw-r--r--docs/textdocs/security_level.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/textdocs/security_level.txt b/docs/textdocs/security_level.txt
index b565ea7966..34d7ce7093 100644
--- a/docs/textdocs/security_level.txt
+++ b/docs/textdocs/security_level.txt
@@ -42,14 +42,14 @@ share. It will send a password along with each "tree connection"
operation. The client is expecting a password to be associated with
each share, independent of the user. This means that samba has to work
out what username the client probably wants to use. It is never
-explicitly sent the username. A "real" SMB server like NT actually
-associates passwords directly with shares in share level security, but
+explicitly sent the username. Some commercial SMB servers such as NT actually
+associate passwords directly with shares in share level security, but
samba always uses the unix authentication scheme where it is a
username/password that is authenticated, not a "share/password".
Many clients send a "session setup" even if the server is in share
level security. They normally send a valid username but no
-password. Samba records this username is a list of "possible
+password. Samba records this username in a list of "possible
usernames". When the client then does a "tree connection" it also adds
to this list the name of the share they try to connect to (useful for
home directories) and any users listed in the "user =" smb.conf
@@ -75,4 +75,5 @@ passwords in encrypted form. You have to compile samba with encryption
enabled to support this feature, and you have to maintain a separate
smbpasswd file with SMB style encrypted passwords. It is
cryptographically impossible to translate from unix style encryption
-to SMB style encryption.
+to SMB style encryption, although there are some fairly simple management
+schemes by which the two could be kept in sync.