From b2ded598ca76ba61bd6efd1598434c986135e723 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Tue, 21 Jun 2005 20:34:29 +0000 Subject: Fixing index problems. (This used to be commit 2e192190776e41ed96ccb77af945e8ab815be526) --- docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) (limited to 'docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml') diff --git a/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml b/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml index ae658e28ea..fa7fdf72b9 100644 --- a/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml +++ b/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml @@ -97,13 +97,12 @@ the Samba server is not a member of a domain security context. local smbpasswd file LDAP backend Winbind -Through the use of Pluggable Authentication Modules (PAM) and the name service switcher (NSS), -which maintains the UNIX-user database, the source of authentication may reside on -another server. We would be inclined to call this the authentication server. -This means that the Samba server may use the local UNIX/Linux system password database -(/etc/passwd or /etc/shadow), may use a -local smbpasswd file, or may use an LDAP backend, or even via PAM and Winbind another CIFS/SMB server -for authentication. +Through the use of Pluggable Authentication Modules (PAM) (see the chapter on PAM) +and the name service switcher (NSS), which maintains the UNIX-user database, the source of authentication may +reside on another server. We would be inclined to call this the authentication server. This means that the +Samba server may use the local UNIX/Linux system password database (/etc/passwd or +/etc/shadow), may use a local smbpasswd file, or may use an LDAP backend, or even via PAM +and Winbind another CIFS/SMB server for authentication. -- cgit