From 2e2a5d50eb0fcbfdab14e56d6150a1bd35d57f28 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Wed, 13 Nov 2002 15:34:49 +0000 Subject: Some more doc updates: - make - update status of docs document - move security_level to 'type of installation' part (This used to be commit 11ad39398e077c3901e63f31bcc6efb223854357) --- docs/htmldocs/securitylevels.html | 92 ++++++++++----------------------------- 1 file changed, 22 insertions(+), 70 deletions(-) (limited to 'docs/htmldocs/securitylevels.html') diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html index 6613e07d5d..f1e9297fca 100644 --- a/docs/htmldocs/securitylevels.html +++ b/docs/htmldocs/securitylevels.html @@ -2,7 +2,7 @@ Security levelsUser and Share security level (for servers not in a domain)PrevNextChapter 15. Security levels

15.1. Introduction

Samba supports the following options to the global smb.conf parameter

[global]
-security = [share|user(default)|server|domain|ads]

Please refer to the smb.conf man page for usage information and to the document -DOMAIN_MEMBER.html for further background details -on domain mode security. The Windows 2000 Kerberos domain security model -(security = ads) is described in the ADS-HOWTO.html.

Of the above, "security = server" means that Samba reports to clients that -it is running in "user mode" but actually passes off all authentication -requests to another "user mode" server. This requires an additional -parameter "password server =" that points to the real authentication server. -That real authentication server can be another Samba server or can be a -Windows NT server, the later natively capable of encrypted password support.

15.2. More complete description of security levels

Chapter 6. User and Share security level (for servers not in a domain)

A SMB server tells the client at startup what "security level" it is running. There are two options "share level" and "user level". Which @@ -214,7 +160,13 @@ smbpasswd file with SMB style encrypted passwords. It is cryptographically impossible to translate from unix style encryption to SMB style encryption, although there are some fairly simple management schemes by which the two could be kept in sync.

"security = server" means that Samba reports to clients that +it is running in "user mode" but actually passes off all authentication +requests to another "user mode" server. This requires an additional +parameter "password server =" that points to the real authentication server. +That real authentication server can be another Samba server or can be a +Windows NT server, the later natively capable of encrypted password support.