diff options
Diffstat (limited to 'docs/htmldocs/pam.html')
| -rw-r--r-- | docs/htmldocs/pam.html | 257 | 
1 files changed, 83 insertions, 174 deletions
diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html index 2b284dd929..ba2bf6c922 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -2,22 +2,24 @@  <HTML  ><HEAD  ><TITLE ->PAM Configuration for Centrally Managed Authentication</TITLE +>Configuring PAM for distributed but centrally  +managed authentication</TITLE  ><META  NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK  REL="HOME"  TITLE="SAMBA Project Documentation"  HREF="samba-howto-collection.html"><LINK  REL="UP" -TITLE="Advanced Configuration" +TITLE="Optional configuration"  HREF="optional.html"><LINK  REL="PREVIOUS" -TITLE="Interdomain Trust Relationships" -HREF="interdomaintrusts.html"><LINK +TITLE="UNIX Permission Bits and Windows NT Access Control Lists" +HREF="unix-permissions.html"><LINK  REL="NEXT" -TITLE="Stackable VFS modules" -HREF="vfs.html"></HEAD +TITLE="Hosting a Microsoft Distributed File System tree on Samba" +HREF="msdfs.html"></HEAD  ><BODY  CLASS="CHAPTER"  BGCOLOR="#FFFFFF" @@ -45,7 +47,7 @@ WIDTH="10%"  ALIGN="left"  VALIGN="bottom"  ><A -HREF="interdomaintrusts.html" +HREF="unix-permissions.html"  ACCESSKEY="P"  >Prev</A  ></TD @@ -59,7 +61,7 @@ WIDTH="10%"  ALIGN="right"  VALIGN="bottom"  ><A -HREF="vfs.html" +HREF="msdfs.html"  ACCESSKEY="N"  >Next</A  ></TD @@ -72,41 +74,14 @@ WIDTH="100%"></DIV  CLASS="CHAPTER"  ><H1  ><A -NAME="PAM" -></A ->Chapter 20. PAM Configuration for Centrally Managed Authentication</H1 -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->20.1. <A -HREF="pam.html#AEN3507" ->Samba and PAM</A -></DT -><DT ->20.2. <A -HREF="pam.html#AEN3558" ->Distributed Authentication</A -></DT -><DT ->20.3. <A -HREF="pam.html#AEN3563" ->PAM Configuration in smb.conf</A -></DT -></DL -></DIV +NAME="PAM">Chapter 12. Configuring PAM for distributed but centrally  +managed authentication</H1  ><DIV  CLASS="SECT1"  ><H1  CLASS="SECT1"  ><A -NAME="AEN3507" ->20.1. Samba and PAM</A -></H1 +NAME="AEN1788">12.1. Samba and PAM</H1  ><P  >A number of Unix systems (eg: Sun Solaris), as well as the   xxxxBSD family and Linux, now utilize the Pluggable Authentication  @@ -141,45 +116,6 @@ or by editing individual files that are located in <TT  CLASS="FILENAME"  >/etc/pam.d</TT  >.</P -><DIV -CLASS="NOTE" -><P -></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->	If the PAM authentication module (loadable link library file) is located in the -	default location then it is not necessary to specify the path. In the case of -	Linux, the default location is <TT -CLASS="FILENAME" ->/lib/security</TT ->. If the module -	is located other than default then the path may be specified as: -	 -	<PRE -CLASS="PROGRAMLISTING" ->	auth       required      /other_path/pam_strange_module.so -	</PRE -> -	</P -></TD -></TR -></TABLE -></DIV  ><P  >The following is an example <TT  CLASS="FILENAME" @@ -195,46 +131,40 @@ CLASS="FILENAME"  ><P  ><PRE  CLASS="PROGRAMLISTING" ->	#%PAM-1.0 -	# The PAM configuration file for the `login' service -	# -	auth 		required	pam_securetty.so -	auth 		required	pam_nologin.so -	# auth 		required	pam_dialup.so -	# auth 		optional	pam_mail.so -	auth		required	pam_pwdb.so shadow md5 -	# account    	requisite  	pam_time.so -	account		required	pam_pwdb.so -	session		required	pam_pwdb.so -	# session 	optional	pam_lastlog.so -	# password   	required   	pam_cracklib.so retry=3 -	password	required	pam_pwdb.so shadow md5</PRE +>#%PAM-1.0 +# The PAM configuration file for the `login' service +# +auth 		required	pam_securetty.so +auth 		required	pam_nologin.so +# auth 		required	pam_dialup.so +# auth 		optional	pam_mail.so +auth		required	pam_pwdb.so shadow md5 +# account    	requisite  	pam_time.so +account		required	pam_pwdb.so +session		required	pam_pwdb.so +# session 	optional	pam_lastlog.so +# password   	required   	pam_cracklib.so retry=3 +password	required	pam_pwdb.so shadow md5</PRE  ></P  ><P  >PAM allows use of replacable modules. Those available on a   sample system include:</P  ><P -><SAMP -CLASS="PROMPT" ->$</SAMP -><KBD -CLASS="USERINPUT" ->/bin/ls /lib/security</KBD -> -<PRE +><PRE  CLASS="PROGRAMLISTING" ->	pam_access.so    pam_ftp.so          pam_limits.so      -	pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so      -	pam_cracklib.so  pam_group.so        pam_listfile.so    -	pam_nologin.so   pam_rootok.so       pam_tally.so       -	pam_deny.so      pam_issue.so        pam_mail.so        -	pam_permit.so    pam_securetty.so    pam_time.so        -	pam_dialup.so    pam_lastlog.so      pam_mkhomedir.so   -	pam_pwdb.so      pam_shells.so       pam_unix.so        -	pam_env.so       pam_ldap.so         pam_motd.so        -	pam_radius.so    pam_smbpass.so      pam_unix_acct.so   -	pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so -	pam_userdb.so    pam_warn.so         pam_unix_session.so</PRE +>$ /bin/ls /lib/security +pam_access.so    pam_ftp.so          pam_limits.so      +pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so      +pam_cracklib.so  pam_group.so        pam_listfile.so    +pam_nologin.so   pam_rootok.so       pam_tally.so       +pam_deny.so      pam_issue.so        pam_mail.so        +pam_permit.so    pam_securetty.so    pam_time.so        +pam_dialup.so    pam_lastlog.so      pam_mkhomedir.so   +pam_pwdb.so      pam_shells.so       pam_unix.so        +pam_env.so       pam_ldap.so         pam_motd.so        +pam_radius.so    pam_smbpass.so      pam_unix_acct.so   +pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so +pam_userdb.so    pam_warn.so         pam_unix_session.so</PRE  ></P  ><P  >The following example for the login program replaces the use of  @@ -297,13 +227,13 @@ source distribution.</P  ><P  ><PRE  CLASS="PROGRAMLISTING" ->	#%PAM-1.0 -	# The PAM configuration file for the `login' service -	# -	auth		required	pam_smbpass.so nodelay -	account		required	pam_smbpass.so nodelay -	session		required	pam_smbpass.so nodelay -	password	required	pam_smbpass.so nodelay</PRE +>#%PAM-1.0 +# The PAM configuration file for the `login' service +# +auth		required	pam_smbpass.so nodelay +account		required	pam_smbpass.so nodelay +session		required	pam_smbpass.so nodelay +password	required	pam_smbpass.so nodelay</PRE  ></P  ><P  >The following is the PAM configuration file for a particular  @@ -314,13 +244,13 @@ CLASS="FILENAME"  ><P  ><PRE  CLASS="PROGRAMLISTING" ->	#%PAM-1.0 -	# The PAM configuration file for the `samba' service -	# -	auth       required     pam_pwdb.so nullok nodelay shadow audit -	account    required     pam_pwdb.so audit nodelay -	session    required     pam_pwdb.so nodelay -	password   required     pam_pwdb.so shadow md5</PRE +>#%PAM-1.0 +# The PAM configuration file for the `samba' service +# +auth       required     /lib/security/pam_pwdb.so nullok nodelay shadow audit +account    required     /lib/security/pam_pwdb.so audit nodelay +session    required     /lib/security/pam_pwdb.so nodelay +password   required     /lib/security/pam_pwdb.so shadow md5</PRE  ></P  ><P  >In the following example the decision has been made to use the  @@ -331,36 +261,16 @@ program.</P  ><P  ><PRE  CLASS="PROGRAMLISTING" ->	#%PAM-1.0 -	# The PAM configuration file for the `samba' service -	# -	auth       required     pam_smbpass.so nodelay -	account    required     pam_pwdb.so audit nodelay -	session    required     pam_pwdb.so nodelay -	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE +>#%PAM-1.0 +# The PAM configuration file for the `samba' service +# +auth       required     /lib/security/pam_smbpass.so nodelay +account    required     /lib/security/pam_pwdb.so audit nodelay +session    required     /lib/security/pam_pwdb.so nodelay +password   required     /lib/security/pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE  ></P -><DIV -CLASS="NOTE"  ><P -></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P ->PAM allows stacking of authentication mechanisms. It is  +>Note: PAM allows stacking of authentication mechanisms. It is   also possible to pass information obtained within one PAM module through   to the next module in the PAM stack. Please refer to the documentation for   your particular system implementation for details regarding the specific  @@ -377,19 +287,13 @@ CLASS="FILENAME"  on the basis that it allows for easier administration. As with all issues in   life though, every decision makes trade-offs, so you may want examine the   PAM documentation for further helpful information.</P -></TD -></TR -></TABLE -></DIV  ></DIV  ><DIV  CLASS="SECT1"  ><H1  CLASS="SECT1"  ><A -NAME="AEN3558" ->20.2. Distributed Authentication</A -></H1 +NAME="AEN1832">12.2. Distributed Authentication</H1  ><P  >The astute administrator will realize from this that the   combination of <TT @@ -399,9 +303,16 @@ CLASS="FILENAME"  <B  CLASS="COMMAND"  >winbindd</B ->, and a distributed  -passdb backend, such as ldap, will allow the establishment of a -centrally managed, distributed  +>, and <B +CLASS="COMMAND" +>rsync</B +> (see +<A +HREF="http://rsync.samba.org/" +TARGET="_top" +>http://rsync.samba.org/</A +>) +will allow the establishment of a centrally managed, distributed   user/password database that can also be used by all   PAM (eg: Linux) aware programs and applications. This arrangement   can have particularly potent advantages compared with the  @@ -413,9 +324,7 @@ CLASS="SECT1"  ><H1  CLASS="SECT1"  ><A -NAME="AEN3563" ->20.3. PAM Configuration in smb.conf</A -></H1 +NAME="AEN1839">12.3. PAM Configuration in smb.conf</H1  ><P  >There is an option in smb.conf called <A  HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS" @@ -424,10 +333,10 @@ TARGET="_top"  >.   The following is from the on-line help for this option in SWAT;</P  ><P ->When Samba is configured to enable PAM support (i.e.  -<CODE +>When Samba 2.2 is configure to enable PAM support (i.e.  +<TT  CLASS="CONSTANT" ->--with-pam</CODE +>--with-pam</TT  >), this parameter will   control whether or not Samba should obey PAM's account   and session management directives. The default behavior  @@ -465,7 +374,7 @@ WIDTH="33%"  ALIGN="left"  VALIGN="top"  ><A -HREF="interdomaintrusts.html" +HREF="unix-permissions.html"  ACCESSKEY="P"  >Prev</A  ></TD @@ -483,7 +392,7 @@ WIDTH="33%"  ALIGN="right"  VALIGN="top"  ><A -HREF="vfs.html" +HREF="msdfs.html"  ACCESSKEY="N"  >Next</A  ></TD @@ -493,7 +402,7 @@ ACCESSKEY="N"  WIDTH="33%"  ALIGN="left"  VALIGN="top" ->Interdomain Trust Relationships</TD +>UNIX Permission Bits and Windows NT Access Control Lists</TD  ><TD  WIDTH="34%"  ALIGN="center" @@ -507,7 +416,7 @@ ACCESSKEY="U"  WIDTH="33%"  ALIGN="right"  VALIGN="top" ->Stackable VFS modules</TD +>Hosting a Microsoft Distributed File System tree on Samba</TD  ></TR  ></TABLE  ></DIV  | 
