diff options
| author | Thorsten Kukuk <kukuk@thkukuk.de> | 2006-06-22 19:44:29 +0000 |
|---|---|---|
| committer | Thorsten Kukuk <kukuk@thkukuk.de> | 2006-06-22 19:44:29 +0000 |
| commit | 1cbeedd65b10f4eee830e3d222519b2701050f77 (patch) | |
| tree | 7195310ae8c00f66bd864b990f16d2927bf1d1d3 | |
| parent | 903c285ef795257c6799bfc8b99d7eb9aa182a25 (diff) | |
Relevant BUGIDs:
Purpose of commit: bugfix
Commit summary:
---------------
2006-06-23 Thorsten Kukuk <kukuk@thkukuk.de>
* modules/pam_access/access.conf.5.xml: Fix syntax for SAG.
* modules/pam_access/pam_access.8.xml: Likewise.
* modules/pam_deny/pam_deny.8.xml: Likewise.
* modules/pam_echo/pam_echo.8.xml: Likewise.
* modules/pam_env/pam_env.8.xml: Likewise.
* modules/pam_env/pam_env.conf.5.xml: Likewise.
* modules/pam_group/group.conf.5.xml: Likewise.
* modules/pam_group/pam_group.8.xml: Likewise.
* modules/pam_limits/limits.conf.5.xml: Likewise.
* modules/pam_listfile/pam_listfile.8.xml: Likewise.
* modules/pam_succeed_if/pam_succeed_if.8.xml: Likewise.
* modules/pam_time/pam_time.8.xml: Likewise.
* modules/pam_time/time.conf.5.xml: Likewise.
* modules/pam_access/access.conf.5: Regenerate.
* modules/pam_access/pam_access.8: Likewise.
* modules/pam_deny/pam_deny.8: Likewise.
* modules/pam_echo/README: Likewise.
* modules/pam_echo/pam_echo.8: Likewise.
* modules/pam_env/pam_env.8: Likewise.
* modules/pam_env/pam_env.conf.5: Likewise.
* modules/pam_group/README: Likewise.
* modules/pam_group/group.conf.5: Likewise.
* modules/pam_group/pam_group.8: Likewise.
* modules/pam_limits/limits.conf.5: Likewise.
* modules/pam_listfile/README: Likewise.
* modules/pam_listfile/pam_listfile.8: Likewise.
* modules/pam_succeed_if/pam_succeed_if.8: Likewise.
* modules/pam_time/pam_time.8: Likewise.
* modules/pam_time/time.conf.5: Likewise.
* doc/man/Makefile.am: Add pam.conf-desc.xml, pam.conf-dir.xml
and pam.conf-syntax.xml.
* doc/man/pam.conf.5.xml: Split into different pieces for SAG.
* doc/man/pam.conf.5: Regenerated.
* doc/man/pam.conf-desc.xml: New.
* doc/man/pam.conf-dir.xml: New.
* doc/man/pam.conf-syntax.xml: New.
36 files changed, 591 insertions, 500 deletions
@@ -1,3 +1,41 @@ +2006-06-23 Thorsten Kukuk <kukuk@thkukuk.de> + + * modules/pam_access/access.conf.5.xml: Fix syntax for SAG. + * modules/pam_access/pam_access.8.xml: Likewise. + * modules/pam_deny/pam_deny.8.xml: Likewise. + * modules/pam_echo/pam_echo.8.xml: Likewise. + * modules/pam_env/pam_env.8.xml: Likewise. + * modules/pam_env/pam_env.conf.5.xml: Likewise. + * modules/pam_group/group.conf.5.xml: Likewise. + * modules/pam_group/pam_group.8.xml: Likewise. + * modules/pam_limits/limits.conf.5.xml: Likewise. + * modules/pam_listfile/pam_listfile.8.xml: Likewise. + * modules/pam_succeed_if/pam_succeed_if.8.xml: Likewise. + * modules/pam_time/pam_time.8.xml: Likewise. + * modules/pam_time/time.conf.5.xml: Likewise. + + * modules/pam_access/access.conf.5: Regenerate. + * modules/pam_access/pam_access.8: Likewise. + * modules/pam_deny/pam_deny.8: Likewise. + * modules/pam_echo/README: Likewise. + * modules/pam_echo/pam_echo.8: Likewise. + * modules/pam_env/pam_env.8: Likewise. + * modules/pam_env/pam_env.conf.5: Likewise. + * modules/pam_group/README: Likewise. + * modules/pam_group/group.conf.5: Likewise. + * modules/pam_group/pam_group.8: Likewise. + * modules/pam_limits/limits.conf.5: Likewise. + * modules/pam_listfile/README: Likewise. + * modules/pam_listfile/pam_listfile.8: Likewise. + * modules/pam_succeed_if/pam_succeed_if.8: Likewise. + * modules/pam_time/pam_time.8: Likewise. + * modules/pam_time/time.conf.5: Likewise. + + * doc/man/Makefile.am: Add pam.conf-desc.xml, pam.conf-dir.xml + and pam.conf-syntax.xml. + * doc/man/pam.conf.5.xml: Split into different pieces for SAG. + * doc/man/pam.conf.5: Regenerated. + 2006-06-21 Thorsten Kukuk <kukuk@thkukuk.de> * modules/pam_selinux/Makefile.am: Fix "make dist" if libselinux diff --git a/doc/man/Makefile.am b/doc/man/Makefile.am index 3ce244a9..78b9e66c 100644 --- a/doc/man/Makefile.am +++ b/doc/man/Makefile.am @@ -36,10 +36,12 @@ XMLS = pam.3.xml pam.8.xml \ pam_sm_close_session.3.xml pam_sm_open_session.3.xml \ pam_sm_setcred.3.xml pam_start.3.xml pam_strerror.3.xml \ pam_sm_chauthtok.3.xml \ - pam_item_types.inc.xml + pam_item_types.inc.xml \ + pam.conf-desc.xml pam.conf-dir.xml pam.conf-syntax.xml if ENABLE_REGENERATE_MAN pam_get_item.3: pam_item_types.inc.xml pam_set_data.3: pam_item_types.inc.xml +pam.conf.5: pam.conf-desc.xml pam.conf-dir.xml pam.conf-syntax.xml -include $(top_srcdir)/Make.xml.rules endif diff --git a/doc/man/pam.conf-desc.xml b/doc/man/pam.conf-desc.xml new file mode 100644 index 00000000..909dcdbe --- /dev/null +++ b/doc/man/pam.conf-desc.xml @@ -0,0 +1,21 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> +<section id='pam.conf-desc'> + <para> + When a <emphasis>PAM</emphasis> aware privilege granting application + is started, it activates its attachment to the PAM-API. This + activation performs a number of tasks, the most important being the + reading of the configuration file(s): <filename>/etc/pam.conf</filename>. + Alternatively, this may be the contents of the + <filename>/etc/pam.d/</filename> directory. The presence of this + directory will cause Linux-PAM to ignore + <filename>/etc/pam.conf</filename>. + </para> + <para> + These files list the <emphasis>PAM</emphasis>s that will do the + authentication tasks required by this service, and the appropriate + behavior of the PAM-API in the event that individual + <emphasis>PAM</emphasis>s fail. + </para> +</section> diff --git a/doc/man/pam.conf-dir.xml b/doc/man/pam.conf-dir.xml new file mode 100644 index 00000000..8446cf35 --- /dev/null +++ b/doc/man/pam.conf-dir.xml @@ -0,0 +1,30 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> +<section id='pam.conf-dir'> + <para> + More flexible than the single configuration file is it to + configure libpam via the contents of the + <filename>/etc/pam.d/</filename> directory. In this case the + directory is filled with files each of which has a filename + equal to a service-name (in lower-case): it is the personal + configuration file for the named service. + </para> + + <para> + The syntax of each file in /etc/pam.d/ is similar to that of the + <filename>/etc/pam.conf</filename> file and is made up of lines + of the following form: + </para> + + <programlisting> +type control module-path module-arguments + </programlisting> + + <para> + The only difference being that the service-name is not present. The + service-name is of course the name of the given configuration file. + For example, <filename>/etc/pam.d/login</filename> contains the + configuration for the <emphasis remap='B'>login</emphasis> service. + </para> +</section> diff --git a/doc/man/pam.conf-syntax.xml b/doc/man/pam.conf-syntax.xml new file mode 100644 index 00000000..b422cba9 --- /dev/null +++ b/doc/man/pam.conf-syntax.xml @@ -0,0 +1,372 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> + +<section id='pam.conf-syntax'> + <para> + The syntax of the <filename>/etc/pam.conf</filename> + configuration file is as follows. The file is made up of a list + of rules, each rule is typically placed on a single line, + but may be extended with an escaped end of line: `\<LF>'. + Comments are preceded with `#' marks and extend to the next end of + line. + </para> + + <para> + The format of each rule is a space separated collection of tokens, + the first three being case-insensitive: + </para> + + <para> + <emphasis remap='B'> service type control module-path module-arguments</emphasis> + </para> + + <para> + The syntax of files contained in the <filename>/etc/pam.d/</filename> + directory, are identical except for the absence of any + <emphasis>service</emphasis> field. In this case, the + <emphasis>service</emphasis> is the name of the file in the + <filename>/etc/pam.d/</filename> directory. This filename must be + in lower case. + </para> + + <para> + An important feature of <emphasis>PAM</emphasis>, is that a + number of rules may be <emphasis>stacked</emphasis> to combine + the services of a number of PAMs for a given authentication task. + </para> + + <para> + The <emphasis>service</emphasis> is typically the familiar name of + the corresponding application: <emphasis>login</emphasis> and + <emphasis>su</emphasis> are good examples. The + <emphasis>service</emphasis>-name, <emphasis>other</emphasis>, + is reserved for giving <emphasis>default</emphasis> rules. + Only lines that mention the current service (or in the absence + of such, the <emphasis>other</emphasis> entries) will be associated + with the given service-application. + </para> + + <para> + The <emphasis>type</emphasis> is the management group that the rule + corresponds to. It is used to specify which of the management groups + the subsequent module is to be associated with. Valid entries are: + </para> + <variablelist> + <varlistentry> + <term>account</term> + <listitem> + <para> + this module type performs non-authentication based account + management. It is typically used to restrict/permit access + to a service based on the time of day, currently available + system resources (maximum number of users) or perhaps the + location of the applicant user -- 'root' login only on the + console. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>auth</term> + <listitem> + <para> + this module type provides two aspects of authenticating + the user. Firstly, it establishes that the user is who they + claim to be, by instructing the application to prompt the user + for a password or other means of identification. Secondly, the + module can grant group membership or other privileges through + its credential granting properties. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>password</term> + <listitem> + <para> + this module type is required for updating the authentication + token associated with the user. Typically, there is one module + for each 'challenge/response' based authentication (auth) type. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>session</term> + <listitem> + <para> + this module type is associated with doing things that need to + be done for the user before/after they can be given service. + Such things include the logging of information concerning the + opening/closing of some data exchange with a user, mounting + directories, etc. + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + The third field, <emphasis>control</emphasis>, indicates the + behavior of the PAM-API should the module fail to succeed in its + authentication task. There are two types of syntax for this control + field: the simple one has a single simple keyword; the more + complicated one involves a square-bracketed selection of + <emphasis>value=action</emphasis> pairs. + </para> + + <para> + For the simple (historical) syntax valid <emphasis>control</emphasis> + values are: + </para> + <variablelist> + <varlistentry> + <term>required</term> + <listitem> + <para> + failure of such a PAM will ultimately lead to the PAM-API + returning failure but only after the remaining + <emphasis>stacked</emphasis> modules (for this + <emphasis>service</emphasis> and <emphasis>type</emphasis>) + have been invoked. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>requisite</term> + <listitem> + <para> + like <emphasis>required</emphasis>, however, in the case that + such a module returns a failure, control is directly returned + to the application. The return value is that associated with + the first required or requisite module to fail. Note, this flag + can be used to protect against the possibility of a user getting + the opportunity to enter a password over an unsafe medium. It is + conceivable that such behavior might inform an attacker of valid + accounts on a system. This possibility should be weighed against + the not insignificant concerns of exposing a sensitive password + in a hostile environment. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>sufficient</term> + <listitem> + <para> + success of such a module is enough to satisfy the + authentication requirements of the stack of modules (if a + prior <emphasis>required</emphasis> module has failed the + success of this one is <emphasis>ignored</emphasis>). A failure + of this module is not deemed as fatal to satisfying the + application that this type has succeeded. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>optional</term> + <listitem> + <para> + the success or failure of this module is only important if + it is the only module in the stack associated with this + <emphasis>service</emphasis>+<emphasis>type</emphasis>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>include</term> + <listitem> + <para> + include all lines of given type from the configuration + file specified as an argument to this control. + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + For the more complicated syntax valid <emphasis>control</emphasis> + values have the following form: + </para> + <programlisting> + [value1=action1 value2=action2 ...] + </programlisting> + + <para> + Where <emphasis>valueN</emphasis> corresponds to the return code + from the function invoked in the module for which the line is + defined. It is selected from one of these: + <emphasis>success</emphasis>, <emphasis>open_err</emphasis>, + <emphasis>symbol_err</emphasis>, <emphasis>service_err</emphasis>, + <emphasis>system_err</emphasis>, <emphasis>buf_err</emphasis>, + <emphasis>perm_denied</emphasis>, <emphasis>auth_err</emphasis>, + <emphasis>cred_insufficient</emphasis>, + <emphasis>authinfo_unavail</emphasis>, + <emphasis>user_unknown</emphasis>, <emphasis>maxtries</emphasis>, + <emphasis>new_authtok_reqd</emphasis>, + <emphasis>acct_expired</emphasis>, <emphasis>session_err</emphasis>, + <emphasis>cred_unavail</emphasis>, <emphasis>cred_expired</emphasis>, + <emphasis>cred_err</emphasis>, <emphasis>no_module_data</emphasis>, + <emphasis>conv_err</emphasis>, <emphasis>authtok_err</emphasis>, + <emphasis>authtok_recover_err</emphasis>, + <emphasis>authtok_lock_busy</emphasis>, + <emphasis>authtok_disable_aging</emphasis>, + <emphasis>try_again</emphasis>, <emphasis>ignore</emphasis>, + <emphasis>abort</emphasis>, <emphasis>authtok_expired</emphasis>, + <emphasis>module_unknown</emphasis>, <emphasis>bad_item</emphasis> + and <emphasis>default</emphasis>. + </para> + <para> + The last of these, <emphasis>default</emphasis>, implies 'all + <emphasis>valueN</emphasis>'s not mentioned explicitly. Note, the + full list of PAM errors is available in + <filename>/usr/include/security/_pam_types.h</filename>. The + <emphasis>actionN</emphasis> can be: an unsigned integer, + <emphasis>n</emphasis>, signifying an action of 'jump over the + next <emphasis>n</emphasis> modules in the stack', or take one + of the following forms: + </para> + <variablelist> + <varlistentry> + <term>ignore</term> + <listitem> + <para> + when used with a stack of modules, the module's return + status will not contribute to the return code the application + obtains. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>bad</term> + <listitem> + <para> + this action indicates that the return code should be thought + of as indicative of the module failing. If this module is the + first in the stack to fail, its status value will be used for + that of the whole stack. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>die</term> + <listitem> + <para> + equivalent to bad with the side effect of terminating the + module stack and PAM immediately returning to the application. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>ok</term> + <listitem> + <para> + this tells PAM that the administrator thinks this return code + should contribute directly to the return code of the full + stack of modules. In other words, if the former state of the + stack would lead to a return of <emphasis>PAM_SUCCESS</emphasis>, + the module's return code will override this value. Note, if + the former state of the stack holds some value that is + indicative of a modules failure, this 'ok' value will not be + used to override that value. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>done</term> + <listitem> + <para> + equivalent to ok with the side effect of terminating the module + stack and PAM immediately returning to the application. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>reset</term> + <listitem> + <para> + clear all memory of the state of the module stack and + start again with the next stacked module. + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + Each of the four keywords: required; requisite; sufficient; and + optional, have an equivalent expression in terms of the [...] + syntax. They are as follows: + </para> + <variablelist> + <varlistentry> + <term>required</term> + <listitem> + <para> + [success=ok new_authtok_reqd=ok ignore=ignore default=bad] + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>requisite</term> + <listitem> + <para> + [success=ok new_authtok_reqd=ok ignore=ignore default=die] + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>sufficient</term> + <listitem> + <para> + [success=done new_authtok_reqd=done default=ignore] + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>optional</term> + <listitem> + <para> + [success=ok new_authtok_reqd=ok default=ignore] + </para> + </listitem> + </varlistentry> + </variablelist> + + <para> + <emphasis>module-path</emphasis> is either the full filename + of the PAM to be used by the application (it begins with a '/'), + or a relative pathname from the default module location: + <filename>/lib/security/</filename> or + <filename>/lib64/security/</filename>, depending on the architecture. + </para> + + <para> + <emphasis>module-arguments</emphasis> are a space separated list + of tokens that can be used to modify the specific behavior of the + given PAM. Such arguments will be documented for each individual + module. Note, if you wish to include spaces in an argument, you + should surround that argument with square brackets. + </para> + <programlisting> + squid auth required pam_mysql.so user=passwd_query passwd=mada \ + db=eminence [query=select user_name from internet_service \ + where user_name='%u' and password=PASSWORD('%p') and \ + service='web_proxy'] + </programlisting> + <para> + When using this convention, you can include `[' characters + inside the string, and if you wish to include a `]' character + inside the string that will survive the argument parsing, you + should use `\['. In other words: + </para> + <programlisting> + [..[..\]..] --> ..[..].. + </programlisting> + + <para> + Any line in (one of) the configuration file(s), that is not formatted + correctly, will generally tend (erring on the side of caution) to make + the authentication process fail. A corresponding error is written to + the system log files with a call to + <citerefentry> + <refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum> + </citerefentry>. + </para> + +</section> diff --git a/doc/man/pam.conf.5 b/doc/man/pam.conf.5 index fcedd7d7..11f8737d 100644 --- a/doc/man/pam.conf.5 +++ b/doc/man/pam.conf.5 @@ -1,11 +1,11 @@ .\" Title: pam.conf .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/19/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM.CONF" "5" "06/19/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM.CONF" "5" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -244,9 +244,19 @@ directory. In this case the directory is filled with files each of which has a f The syntax of each file in /etc/pam.d/ is similar to that of the \fI/etc/pam.conf\fR file and is made up of lines of the following form: +.sp +.RS 3n +.nf +type control module\-path module\-arguments + +.fi +.RE .PP - -\fB type control module\-path module\-arguments\fR +The only difference being that the service\-name is not present. The service\-name is of course the name of the given configuration file. For example, +\fI/etc/pam.d/login\fR +contains the configuration for the +\fBlogin\fR +service. .SH "SEE ALSO" .PP diff --git a/doc/man/pam.conf.5.xml b/doc/man/pam.conf.5.xml index d744dac0..68f576af 100644 --- a/doc/man/pam.conf.5.xml +++ b/doc/man/pam.conf.5.xml @@ -19,409 +19,17 @@ <refsect1 id='pam.conf-description'> <title>DESCRIPTION</title> - <para> - When a <emphasis>PAM</emphasis> aware privilege granting application - is started, it activates its attachment to the PAM-API. This - activation performs a number of tasks, the most important being the - reading of the configuration file(s): <filename>/etc/pam.conf</filename>. - Alternatively, this may be the contents of the - <filename>/etc/pam.d/</filename> directory. The presence of this - directory will cause Linux-PAM to ignore - <filename>/etc/pam.conf</filename>. - </para> - - <para> - These files list the <emphasis>PAM</emphasis>s that will do the - authentication tasks required by this service, and the appropriate - behavior of the PAM-API in the event that individual - <emphasis>PAM</emphasis>s fail. - </para> - - <para> - The syntax of the <filename>/etc/pam.conf</filename> - configuration file is as follows. The file is made up of a list - of rules, each rule is typically placed on a single line, - but may be extended with an escaped end of line: `\<LF>'. - Comments are preceded with `#' marks and extend to the next end of - line. - </para> - - <para> - The format of each rule is a space separated collection of tokens, - the first three being case-insensitive: - </para> - - <para> - <emphasis remap='B'> service type control module-path module-arguments</emphasis> - </para> - - <para> - The syntax of files contained in the <filename>/etc/pam.d/</filename> - directory, are identical except for the absence of any - <emphasis>service</emphasis> field. In this case, the - <emphasis>service</emphasis> is the name of the file in the - <filename>/etc/pam.d/</filename> directory. This filename must be - in lower case. - </para> - - <para> - An important feature of <emphasis>PAM</emphasis>, is that a - number of rules may be <emphasis>stacked</emphasis> to combine - the services of a number of PAMs for a given authentication task. - </para> - - <para> - The <emphasis>service</emphasis> is typically the familiar name of - the corresponding application: <emphasis>login</emphasis> and - <emphasis>su</emphasis> are good examples. The - <emphasis>service</emphasis>-name, <emphasis>other</emphasis>, - is reserved for giving <emphasis>default</emphasis> rules. - Only lines that mention the current service (or in the absence - of such, the <emphasis>other</emphasis> entries) will be associated - with the given service-application. - </para> - - <para> - The <emphasis>type</emphasis> is the management group that the rule - corresponds to. It is used to specify which of the management groups - the subsequent module is to be associated with. Valid entries are: - </para> - <variablelist> - <varlistentry> - <term>account</term> - <listitem> - <para> - this module type performs non-authentication based account - management. It is typically used to restrict/permit access - to a service based on the time of day, currently available - system resources (maximum number of users) or perhaps the - location of the applicant user -- 'root' login only on the - console. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>auth</term> - <listitem> - <para> - this module type provides two aspects of authenticating - the user. Firstly, it establishes that the user is who they - claim to be, by instructing the application to prompt the user - for a password or other means of identification. Secondly, the - module can grant group membership or other privileges through - its credential granting properties. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>password</term> - <listitem> - <para> - this module type is required for updating the authentication - token associated with the user. Typically, there is one module - for each 'challenge/response' based authentication (auth) type. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>session</term> - <listitem> - <para> - this module type is associated with doing things that need to - be done for the user before/after they can be given service. - Such things include the logging of information concerning the - opening/closing of some data exchange with a user, mounting - directories, etc. - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - The third field, <emphasis>control</emphasis>, indicates the - behavior of the PAM-API should the module fail to succeed in its - authentication task. There are two types of syntax for this control - field: the simple one has a single simple keyword; the more - complicated one involves a square-bracketed selection of - <emphasis>value=action</emphasis> pairs. - </para> - - <para> - For the simple (historical) syntax valid <emphasis>control</emphasis> - values are: - </para> - <variablelist> - <varlistentry> - <term>required</term> - <listitem> - <para> - failure of such a PAM will ultimately lead to the PAM-API - returning failure but only after the remaining - <emphasis>stacked</emphasis> modules (for this - <emphasis>service</emphasis> and <emphasis>type</emphasis>) - have been invoked. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>requisite</term> - <listitem> - <para> - like <emphasis>required</emphasis>, however, in the case that - such a module returns a failure, control is directly returned - to the application. The return value is that associated with - the first required or requisite module to fail. Note, this flag - can be used to protect against the possibility of a user getting - the opportunity to enter a password over an unsafe medium. It is - conceivable that such behavior might inform an attacker of valid - accounts on a system. This possibility should be weighed against - the not insignificant concerns of exposing a sensitive password - in a hostile environment. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>sufficient</term> - <listitem> - <para> - success of such a module is enough to satisfy the - authentication requirements of the stack of modules (if a - prior <emphasis>required</emphasis> module has failed the - success of this one is <emphasis>ignored</emphasis>). A failure - of this module is not deemed as fatal to satisfying the - application that this type has succeeded. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>optional</term> - <listitem> - <para> - the success or failure of this module is only important if - it is the only module in the stack associated with this - <emphasis>service</emphasis>+<emphasis>type</emphasis>. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>include</term> - <listitem> - <para> - include all lines of given type from the configuration - file specified as an argument to this control. - </para> - </listitem> - </varlistentry> - </variablelist> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" + href="pam.conf-desc.xml" + xpointer='xpointer(//section[@id = "pam.conf-desc"]/*)' /> - <para> - For the more complicated syntax valid <emphasis>control</emphasis> - values have the following form: - </para> - <programlisting> - [value1=action1 value2=action2 ...] - </programlisting> - - <para> - Where <emphasis>valueN</emphasis> corresponds to the return code - from the function invoked in the module for which the line is - defined. It is selected from one of these: - <emphasis>success</emphasis>, <emphasis>open_err</emphasis>, - <emphasis>symbol_err</emphasis>, <emphasis>service_err</emphasis>, - <emphasis>system_err</emphasis>, <emphasis>buf_err</emphasis>, - <emphasis>perm_denied</emphasis>, <emphasis>auth_err</emphasis>, - <emphasis>cred_insufficient</emphasis>, - <emphasis>authinfo_unavail</emphasis>, - <emphasis>user_unknown</emphasis>, <emphasis>maxtries</emphasis>, - <emphasis>new_authtok_reqd</emphasis>, - <emphasis>acct_expired</emphasis>, <emphasis>session_err</emphasis>, - <emphasis>cred_unavail</emphasis>, <emphasis>cred_expired</emphasis>, - <emphasis>cred_err</emphasis>, <emphasis>no_module_data</emphasis>, - <emphasis>conv_err</emphasis>, <emphasis>authtok_err</emphasis>, - <emphasis>authtok_recover_err</emphasis>, - <emphasis>authtok_lock_busy</emphasis>, - <emphasis>authtok_disable_aging</emphasis>, - <emphasis>try_again</emphasis>, <emphasis>ignore</emphasis>, - <emphasis>abort</emphasis>, <emphasis>authtok_expired</emphasis>, - <emphasis>module_unknown</emphasis>, <emphasis>bad_item</emphasis> - and <emphasis>default</emphasis>. - </para> - <para> - The last of these, <emphasis>default</emphasis>, implies 'all - <emphasis>valueN</emphasis>'s not mentioned explicitly. Note, the - full list of PAM errors is available in - <filename>/usr/include/security/_pam_types.h</filename>. The - <emphasis>actionN</emphasis> can be: an unsigned integer, - <emphasis>n</emphasis>, signifying an action of 'jump over the - next <emphasis>n</emphasis> modules in the stack', or take one - of the following forms: - </para> - <variablelist> - <varlistentry> - <term>ignore</term> - <listitem> - <para> - when used with a stack of modules, the module's return - status will not contribute to the return code the application - obtains. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>bad</term> - <listitem> - <para> - this action indicates that the return code should be thought - of as indicative of the module failing. If this module is the - first in the stack to fail, its status value will be used for - that of the whole stack. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>die</term> - <listitem> - <para> - equivalent to bad with the side effect of terminating the - module stack and PAM immediately returning to the application. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>ok</term> - <listitem> - <para> - this tells PAM that the administrator thinks this return code - should contribute directly to the return code of the full - stack of modules. In other words, if the former state of the - stack would lead to a return of <emphasis>PAM_SUCCESS</emphasis>, - the module's return code will override this value. Note, if - the former state of the stack holds some value that is - indicative of a modules failure, this 'ok' value will not be - used to override that value. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>done</term> - <listitem> - <para> - equivalent to ok with the side effect of terminating the module - stack and PAM immediately returning to the application. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>reset</term> - <listitem> - <para> - clear all memory of the state of the module stack and - start again with the next stacked module. - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - Each of the four keywords: required; requisite; sufficient; and - optional, have an equivalent expression in terms of the [...] - syntax. They are as follows: - </para> - <variablelist> - <varlistentry> - <term>required</term> - <listitem> - <para> - [success=ok new_authtok_reqd=ok ignore=ignore default=bad] - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>requisite</term> - <listitem> - <para> - [success=ok new_authtok_reqd=ok ignore=ignore default=die] - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>sufficient</term> - <listitem> - <para> - [success=done new_authtok_reqd=done default=ignore] - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>optional</term> - <listitem> - <para> - [success=ok new_authtok_reqd=ok default=ignore] - </para> - </listitem> - </varlistentry> - </variablelist> - - <para> - <emphasis>module-path</emphasis> is either the full filename - of the PAM to be used by the application (it begins with a '/'), - or a relative pathname from the default module location: - <filename>/lib/security/</filename> or - <filename>/lib64/security/</filename>, depending on the architecture. - </para> - - <para> - <emphasis>module-arguments</emphasis> are a space separated list - of tokens that can be used to modify the specific behavior of the - given PAM. Such arguments will be documented for each individual - module. Note, if you wish to include spaces in an argument, you - should surround that argument with square brackets. - </para> - <programlisting> - squid auth required pam_mysql.so user=passwd_query passwd=mada \ - db=eminence [query=select user_name from internet_service \ - where user_name='%u' and password=PASSWORD('%p') and \ - service='web_proxy'] - </programlisting> - <para> - When using this convention, you can include `[' characters - inside the string, and if you wish to include a `]' character - inside the string that will survive the argument parsing, you - should use `\['. In other words: - </para> - <programlisting> - [..[..\]..] --> ..[..].. - </programlisting> - - <para> - Any line in (one of) the configuration file(s), that is not formatted - correctly, will generally tend (erring on the side of caution) to make - the authentication process fail. A corresponding error is written to - the system log files with a call to - <citerefentry> - <refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum> - </citerefentry>. - </para> - - <para> - More flexible than the single configuration file is it to - configure libpam via the contents of the - <filename>/etc/pam.d/</filename> directory. In this case the - directory is filled with files each of which has a filename - equal to a service-name (in lower-case): it is the personal - configuration file for the named service. - </para> - - <para> - The syntax of each file in /etc/pam.d/ is similar to that of the - <filename>/etc/pam.conf</filename> file and is made up of lines - of the following form: - </para> - - <para> - <emphasis remap='B'> type control module-path module-arguments</emphasis> - </para> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" + href="pam.conf-syntax.xml" + xpointer='xpointer(//section[@id = "pam.conf-syntax"]/*)' /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" + href="pam.conf-dir.xml" + xpointer='xpointer(//section[@id = "pam.conf-dir"]/*)' /> </refsect1> <refsect1 id='pam.conf-see_also'> diff --git a/modules/pam_access/access.conf.5 b/modules/pam_access/access.conf.5 index d9fcddf7..43cc4fce 100644 --- a/modules/pam_access/access.conf.5 +++ b/modules/pam_access/access.conf.5 @@ -1,11 +1,11 @@ .\" Title: access.conf .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/02/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "ACCESS.CONF" "5" "06/02/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "ACCESS.CONF" "5" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -14,8 +14,6 @@ access.conf \- the login access control table file .SH "DESCRIPTION" .PP -This module provides logdaemon style login access control based on login names and on host (or domain) names, internet addresses (or network numbers), on terminal line names in case of non\-networked logins or on service name if called by a daemon. -.PP The \fI/etc/security/access.conf\fR file specifies (\fIuser\fR, diff --git a/modules/pam_access/access.conf.5.xml b/modules/pam_access/access.conf.5.xml index 5d86c56b..492f995d 100644 --- a/modules/pam_access/access.conf.5.xml +++ b/modules/pam_access/access.conf.5.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding='UTF-8'?> -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" - "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"> +<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" + "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"> <refentry id="access.conf"> @@ -18,14 +18,6 @@ <refsect1 id='access.conf-description'> <title>DESCRIPTION</title> - - <para> - This module provides logdaemon style login access control based - on login names and on host (or domain) names, internet addresses - (or network numbers), on terminal line names in case of - non-networked logins or on service name if called by a daemon. - </para> - <para> The <filename>/etc/security/access.conf</filename> file specifies (<replaceable>user</replaceable>, <replaceable>host</replaceable>), @@ -33,7 +25,6 @@ (<replaceable>user</replaceable>, <replaceable>tty</replaceable>) combinations for which a login will be either accepted or refused. </para> - <para> When someone logs in, the file <filename>access.conf</filename> is scanned for the first entry that matches the diff --git a/modules/pam_access/pam_access.8 b/modules/pam_access/pam_access.8 index 814878ca..de86275f 100644 --- a/modules/pam_access/pam_access.8 +++ b/modules/pam_access/pam_access.8 @@ -1,11 +1,11 @@ .\" Title: pam_access .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/02/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_ACCESS" "8" "06/02/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_ACCESS" "8" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -81,4 +81,4 @@ Default configuration file \fBpam\fR(8). .SH "AUTHORS" .PP -The logdaemon style login access control scheme was designed and implemented by Wietse Venema. The pam_access PAM module was developed by Alexei Nogin <alexei@nogin.dnttm.ru>. The IPv4(/) IPv6 support and the network(address) / netmask feature was developed and provided by Mike Becher <mike.becher@lrz\-muenchen.de>. +The logdaemon style login access control scheme was designed and implemented by Wietse Venema. The pam_access PAM module was developed by Alexei Nogin <alexei@nogin.dnttm.ru>. The IPv6 support and the network(address) / netmask feature was developed and provided by Mike Becher <mike.becher@lrz\-muenchen.de>. diff --git a/modules/pam_access/pam_access.8.xml b/modules/pam_access/pam_access.8.xml index d374ac50..a7a28d4a 100644 --- a/modules/pam_access/pam_access.8.xml +++ b/modules/pam_access/pam_access.8.xml @@ -213,7 +213,7 @@ Wietse Venema. The pam_access PAM module was developed by Alexei Nogin <alexei@nogin.dnttm.ru>. - The IPv4(/) IPv6 support and the network(address) / netmask feature + The IPv6 support and the network(address) / netmask feature was developed and provided by Mike Becher <mike.becher@lrz-muenchen.de>. </para> </refsect1> diff --git a/modules/pam_deny/pam_deny.8 b/modules/pam_deny/pam_deny.8 index 089048a3..f9f2d439 100644 --- a/modules/pam_deny/pam_deny.8 +++ b/modules/pam_deny/pam_deny.8 @@ -1,11 +1,11 @@ .\" Title: pam_deny .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/09/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_DENY" "8" "06/09/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_DENY" "8" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -19,6 +19,9 @@ pam_deny \- The locking\-out PAM module .PP This module can be used to deny access. It always indicates a failure to the application through the PAM framework. It might be suitable for using for default (the \fIOTHER\fR) entries. +.SH "OPTIONS" +.PP +This module does not recognice any options. .SH "MODULE SERVICES PROVIDED" .PP All services (\fBaccount\fR, diff --git a/modules/pam_deny/pam_deny.8.xml b/modules/pam_deny/pam_deny.8.xml index cb88605e..91916003 100644 --- a/modules/pam_deny/pam_deny.8.xml +++ b/modules/pam_deny/pam_deny.8.xml @@ -33,6 +33,11 @@ </refsect1> + <refsect1 id="pam_deny-options"> + <title>OPTIONS</title> + <para>This module does not recognice any options.</para> + </refsect1> + <refsect1 id="pam_deny-services"> <title>MODULE SERVICES PROVIDED</title> <para> diff --git a/modules/pam_echo/README b/modules/pam_echo/README index 103e0b03..fca26b77 100644 --- a/modules/pam_echo/README +++ b/modules/pam_echo/README @@ -46,5 +46,5 @@ password required pam_unix.so AUTHOR -Thorsten Kukuk <kukuk@suse.de> +Thorsten Kukuk <kukuk@thkukuk.de> diff --git a/modules/pam_echo/pam_echo.8 b/modules/pam_echo/pam_echo.8 index c4fef137..423a8e1b 100644 --- a/modules/pam_echo/pam_echo.8 +++ b/modules/pam_echo/pam_echo.8 @@ -1,11 +1,11 @@ .\" Title: pam_echo .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/02/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_ECHO" "8" "06/02/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_ECHO" "8" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -85,4 +85,4 @@ password required pam_unix.so \fBpam\fR(8) .SH "AUTHOR" .PP -Thorsten Kukuk <kukuk@suse.de> +Thorsten Kukuk <kukuk@thkukuk.de> diff --git a/modules/pam_echo/pam_echo.8.xml b/modules/pam_echo/pam_echo.8.xml index 3619dd34..4a495195 100644 --- a/modules/pam_echo/pam_echo.8.xml +++ b/modules/pam_echo/pam_echo.8.xml @@ -104,7 +104,7 @@ </refsect1> - <refsect1 id="pam_access-return_values"> + <refsect1 id="pam_echo-return_values"> <title>RETURN VALUES</title> <variablelist> <varlistentry> @@ -163,6 +163,6 @@ password required pam_unix.so <refsect1 id='pam_echo-author'> <title>AUTHOR</title> - <para>Thorsten Kukuk <kukuk@suse.de></para> + <para>Thorsten Kukuk <kukuk@thkukuk.de></para> </refsect1> </refentry> diff --git a/modules/pam_env/pam_env.8 b/modules/pam_env/pam_env.8 index 23083da0..e7746de3 100644 --- a/modules/pam_env/pam_env.8 +++ b/modules/pam_env/pam_env.8 @@ -1,11 +1,11 @@ .\" Title: pam_env .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/02/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_ENV" "8" "06/02/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_ENV" "8" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -84,6 +84,6 @@ Default environment file \fBpam_env.conf\fR(5), \fBpam.d\fR(8), \fBpam\fR(8). -.SH "AUTHORS" +.SH "AUTHOR" .PP pam_env was written by Dave Kinchlea <kinch@kinch.ark.com>. diff --git a/modules/pam_env/pam_env.8.xml b/modules/pam_env/pam_env.8.xml index 4ab305ec..731c20b2 100644 --- a/modules/pam_env/pam_env.8.xml +++ b/modules/pam_env/pam_env.8.xml @@ -198,7 +198,7 @@ </refsect1> <refsect1 id="pam_env-authors"> - <title>AUTHORS</title> + <title>AUTHOR</title> <para> pam_env was written by Dave Kinchlea <kinch@kinch.ark.com>. </para> diff --git a/modules/pam_env/pam_env.conf.5 b/modules/pam_env/pam_env.conf.5 index 3f4dcd4f..17c1a19d 100644 --- a/modules/pam_env/pam_env.conf.5 +++ b/modules/pam_env/pam_env.conf.5 @@ -1,11 +1,11 @@ .\" Title: pam_env.conf .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/02/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_ENV.CONF" "5" "06/02/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_ENV.CONF" "5" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -15,13 +15,9 @@ pam_env.conf \- the environment variables config file .SH "DESCRIPTION" .PP The -\fIpam_env\fR -module allows the (un)setting of environment variables. Supported is the use of previously set environment variables as well as -\fIPAM_ITEM\fRs such as PAM_RHOST. -.PP -The \fI/etc/security/pam_env.conf\fR -file specifies the environment variables to be set, unset or modified. When someone logs in, this file is read and the environment variables are set according. +file specifies the environment variables to be set, unset or modified by +\fBpam_env\fR(8). When someone logs in, this file is read and the environment variables are set according. .PP Each line starts with the variable name, there are then two possible options for each variable DEFAULT and OVERRIDE. DEFAULT allows and administrator to set the value of the variable to some default value, if none is supplied then the empty string is assumed. The OVERRIDE option tells pam_env that it should enter in its value (overriding the default value) if there is one to use. OVERRIDE is not used, "" is assumed and no override will be done. .PP @@ -86,6 +82,6 @@ Silly examples of escaped variables, just to show how they work. \fBpam_env\fR(8), \fBpam.d\fR(5), \fBpam\fR(8) -.SH "AUTHORS" +.SH "AUTHOR" .PP pam_env was written by Dave Kinchlea <kinch@kinch.ark.com>. diff --git a/modules/pam_env/pam_env.conf.5.xml b/modules/pam_env/pam_env.conf.5.xml index 7d12cfe1..090e0e75 100644 --- a/modules/pam_env/pam_env.conf.5.xml +++ b/modules/pam_env/pam_env.conf.5.xml @@ -20,17 +20,11 @@ <title>DESCRIPTION</title> <para> - The <emphasis>pam_env</emphasis> module allows the (un)setting - of environment variables. Supported is the use of previously set - environment variables as well as <emphasis>PAM_ITEM</emphasis>s - such as PAM_RHOST. - </para> - - <para> The <filename>/etc/security/pam_env.conf</filename> file specifies - the environment variables to be set, unset or modified. - When someone logs in, this file is - read and the environment variables are set according. + the environment variables to be set, unset or modified by + <citerefentry><refentrytitle>pam_env</refentrytitle><manvolnum>8</manvolnum></citerefentry>. + When someone logs in, this file is read and the environment + variables are set according. </para> <para> Each line starts with the variable name, there are then two possible @@ -121,7 +115,7 @@ </refsect1> <refsect1 id="pam_env.conf-author"> - <title>AUTHORS</title> + <title>AUTHOR</title> <para> pam_env was written by Dave Kinchlea <kinch@kinch.ark.com>. </para> diff --git a/modules/pam_group/README b/modules/pam_group/README index 71359bf1..2e1e37a5 100644 --- a/modules/pam_group/README +++ b/modules/pam_group/README @@ -40,6 +40,6 @@ Running 'xsh' on tty* (any ttyXXX device), the user 'sword' is given access to games (through membership of the floppy group) after work hours. xsh; tty* ;sword;!Wk0900-1800;games, sound - xsh; tty* ;*;Al0900-1800;floppy + diff --git a/modules/pam_group/group.conf.5 b/modules/pam_group/group.conf.5 index 3c597c7c..0e36ebf4 100644 --- a/modules/pam_group/group.conf.5 +++ b/modules/pam_group/group.conf.5 @@ -1,11 +1,11 @@ .\" Title: group.conf .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/09/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "GROUP.CONF" "5" "06/09/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "GROUP.CONF" "5" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -56,20 +56,28 @@ These are some example lines which might be specified in \fI/etc/security/group.conf\fR. .PP Running 'xsh' on tty* (any ttyXXX device), the user 'us' is given access to the floppy (through membership of the floppy group) -.PP +.sp +.RS 3n +.nf xsh;tty*&!ttyp*;us;Al0000\-2400;floppy +.fi +.RE .PP Running 'xsh' on tty* (any ttyXXX device), the user 'sword' is given access to games (through membership of the floppy group) after work hours. -.PP +.sp +.RS 3n +.nf xsh; tty* ;sword;!Wk0900\-1800;games, sound -.PP xsh; tty* ;*;Al0900\-1800;floppy + +.fi +.RE .SH "SEE ALSO" .PP \fBpam_group\fR(8), \fBpam.d\fR(5), \fBpam\fR(8) -.SH "AUTHORS" +.SH "AUTHOR" .PP pam_group was written by Andrew G. Morgan <morgan@kernel.org>. diff --git a/modules/pam_group/group.conf.5.xml b/modules/pam_group/group.conf.5.xml index 7cab1d49..9c008eb0 100644 --- a/modules/pam_group/group.conf.5.xml +++ b/modules/pam_group/group.conf.5.xml @@ -101,15 +101,16 @@ Running 'xsh' on tty* (any ttyXXX device), the user 'us' is given access to the floppy (through membership of the floppy group) </para> - <para>xsh;tty*&!ttyp*;us;Al0000-2400;floppy</para> + <programlisting>xsh;tty*&!ttyp*;us;Al0000-2400;floppy</programlisting> <para> Running 'xsh' on tty* (any ttyXXX device), the user 'sword' is given access to games (through membership of the floppy group) after work hours. </para> - <para>xsh; tty* ;sword;!Wk0900-1800;games, sound</para> - <para>xsh; tty* ;*;Al0900-1800;floppy</para> - + <programlisting> +xsh; tty* ;sword;!Wk0900-1800;games, sound +xsh; tty* ;*;Al0900-1800;floppy + </programlisting> </refsect1> <refsect1 id="group.conf-see_also"> @@ -122,7 +123,7 @@ </refsect1> <refsect1 id="group.conf-author"> - <title>AUTHORS</title> + <title>AUTHOR</title> <para> pam_group was written by Andrew G. Morgan <morgan@kernel.org>. </para> diff --git a/modules/pam_group/pam_group.8 b/modules/pam_group/pam_group.8 index a72a66dc..7058f1aa 100644 --- a/modules/pam_group/pam_group.8 +++ b/modules/pam_group/pam_group.8 @@ -1,11 +1,11 @@ .\" Title: pam_group .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/02/2006 +.\" Date: 06/22/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_GROUP" "8" "06/02/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_GROUP" "8" "06/22/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -36,6 +36,9 @@ file. If the user is granted any groups based on the behavior of this module, th to those entries \fI/etc/group\fR (or equivalent). +.SH "OPTIONS" +.PP +This module does not recognice any options. .SH "MODULE SERVICES PROVIDED" .PP Only the diff --git a/modules/pam_group/pam_group.8.xml b/modules/pam_group/pam_group.8.xml index 6e6c0498..61c7eef1 100644 --- a/modules/pam_group/pam_group.8.xml +++ b/modules/pam_group/pam_group.8.xml @@ -60,6 +60,11 @@ </para> </refsect1> + <refsect1 id="pam_group-options"> + <title>OPTIONS</title> + <para>This module does not recognice any options.</para> + </refsect1> + <refsect1 id="pam_group-services"> <title>MODULE SERVICES PROVIDED</title> <para> diff --git a/modules/pam_limits/limits.conf.5 b/modules/pam_limits/limits.conf.5 index a8a58213..e6ba853f 100644 --- a/modules/pam_limits/limits.conf.5 +++ b/modules/pam_limits/limits.conf.5 @@ -1,11 +1,11 @@ .\" Title: limits.conf .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/17/2006 +.\" Date: 06/22/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "LIMITS.CONF" "5" "06/17/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "LIMITS.CONF" "5" "06/22/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -14,8 +14,6 @@ limits.conf \- configuration file for the pam_limits module .SH "DESCRIPTION" .PP -The pam_limits PAM module sets limits on the system resources that can be obtained in a user\-session. -.PP The syntax of the lines is as follows: .PP @@ -169,6 +167,6 @@ ftp hard nproc 0 \fBpam_limits\fR(8), \fBpam.d\fR(5), \fBpam\fR(8) -.SH "AUTHORS" +.SH "AUTHOR" .PP pam_limits was initially written by Cristian Gafton <gafton@redhat.com> diff --git a/modules/pam_limits/limits.conf.5.xml b/modules/pam_limits/limits.conf.5.xml index 2f255ea5..28df7381 100644 --- a/modules/pam_limits/limits.conf.5.xml +++ b/modules/pam_limits/limits.conf.5.xml @@ -17,16 +17,9 @@ <refsect1 id='limits.conf-description'> <title>DESCRIPTION</title> - - <para> - The pam_limits PAM module sets limits on the system resources that can be - obtained in a user-session. - </para> - <para> The syntax of the lines is as follows: </para> - <para> <replaceable><domain></replaceable> <replaceable><type></replaceable> <replaceable><item></replaceable> <replaceable><value></replaceable> @@ -285,7 +278,7 @@ ftp hard nproc 0 </refsect1> <refsect1 id="limits.conf-author"> - <title>AUTHORS</title> + <title>AUTHOR</title> <para> pam_limits was initially written by Cristian Gafton <gafton@redhat.com> </para> diff --git a/modules/pam_listfile/README b/modules/pam_listfile/README index 4bfabe2d..f0aaaf7f 100644 --- a/modules/pam_listfile/README +++ b/modules/pam_listfile/README @@ -1,4 +1,4 @@ -pam_listfile — deny or allow services based on an arbitrary file. +pam_listfile — deny or allow services based on an arbitrary file ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ diff --git a/modules/pam_listfile/pam_listfile.8 b/modules/pam_listfile/pam_listfile.8 index 826d337e..2ccecd4b 100644 --- a/modules/pam_listfile/pam_listfile.8 +++ b/modules/pam_listfile/pam_listfile.8 @@ -1,17 +1,17 @@ .\" Title: pam_listfile .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/02/2006 +.\" Date: 06/22/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_LISTFILE" "8" "06/02/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_LISTFILE" "8" "06/22/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .SH "NAME" -pam_listfile \- deny or allow services based on an arbitrary file. +pam_listfile \- deny or allow services based on an arbitrary file .SH "SYNOPSIS" .HP 16 \fBpam_listfile.so\fR item=[tty|user|rhost|ruser|group|shell] sense=[allow|deny] file=\fI/path/filename\fR onerr=[succeed|fail] [apply=[\fIuser\fR|\fI@group\fR]] diff --git a/modules/pam_listfile/pam_listfile.8.xml b/modules/pam_listfile/pam_listfile.8.xml index 85489d3c..0e90414a 100644 --- a/modules/pam_listfile/pam_listfile.8.xml +++ b/modules/pam_listfile/pam_listfile.8.xml @@ -12,7 +12,7 @@ <refnamediv id="pam_listfile-name"> <refname>pam_listfile</refname> - <refpurpose>deny or allow services based on an arbitrary file.</refpurpose> + <refpurpose>deny or allow services based on an arbitrary file</refpurpose> </refnamediv> <refsynopsisdiv> diff --git a/modules/pam_succeed_if/pam_succeed_if.8 b/modules/pam_succeed_if/pam_succeed_if.8 index ee6007cd..4603eba1 100644 --- a/modules/pam_succeed_if/pam_succeed_if.8 +++ b/modules/pam_succeed_if/pam_succeed_if.8 @@ -1,11 +1,11 @@ .\" Title: pam_succeed_if .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/17/2006 +.\" Date: 06/22/2006 .\" Manual: Linux\-PAM .\" Source: Linux\-PAM .\" -.TH "PAM_SUCCEED_IF" "8" "06/17/2006" "Linux\-PAM" "Linux\-PAM" +.TH "PAM_SUCCEED_IF" "8" "06/22/2006" "Linux\-PAM" "Linux\-PAM" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -86,6 +86,13 @@ User is in given group. .TP 3n \fBuser notingroup group\fR User is not in given group. +.SH "MODULE SERVICES PROVIDED" +.PP +The +\fBauth\fR +and +\fBaccount\fR +services are supported. .SH "RETURN VALUES" .TP 3n PAM_SUCCESS diff --git a/modules/pam_succeed_if/pam_succeed_if.8.xml b/modules/pam_succeed_if/pam_succeed_if.8.xml index 5df72628..3a77505d 100644 --- a/modules/pam_succeed_if/pam_succeed_if.8.xml +++ b/modules/pam_succeed_if/pam_succeed_if.8.xml @@ -190,7 +190,15 @@ </variablelist> </refsect1> - <refsect1 id='pam_exec-return_values'> + <refsect1 id="pam_succeed_if-services"> + <title>MODULE SERVICES PROVIDED</title> + <para> + The <emphasis remap='B'>auth</emphasis> and + <emphasis remap='B'>account</emphasis> services are supported. + </para> + </refsect1> + + <refsect1 id='pam_succeed_if-return_values'> <title>RETURN VALUES</title> <variablelist> diff --git a/modules/pam_time/pam_time.8 b/modules/pam_time/pam_time.8 index 58b94ec6..89506830 100644 --- a/modules/pam_time/pam_time.8 +++ b/modules/pam_time/pam_time.8 @@ -1,11 +1,11 @@ .\" Title: pam_time .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/09/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "PAM_TIME" "8" "06/09/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_TIME" "8" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -67,6 +67,6 @@ login account required pam_time.so \fBtime.conf\fR(5), \fBpam.d\fR(8), \fBpam\fR(8). -.SH "AUTHORS" +.SH "AUTHOR" .PP pam_time was written by Andrew G. Morgan <morgan@kernel.org>. diff --git a/modules/pam_time/pam_time.8.xml b/modules/pam_time/pam_time.8.xml index da245ed0..1ec7eb0e 100644 --- a/modules/pam_time/pam_time.8.xml +++ b/modules/pam_time/pam_time.8.xml @@ -140,7 +140,7 @@ login account required pam_time.so </refsect1> <refsect1 id="pam_time-authors"> - <title>AUTHORS</title> + <title>AUTHOR</title> <para> pam_time was written by Andrew G. Morgan <morgan@kernel.org>. </para> diff --git a/modules/pam_time/time.conf.5 b/modules/pam_time/time.conf.5 index e610821d..400344a6 100644 --- a/modules/pam_time/time.conf.5 +++ b/modules/pam_time/time.conf.5 @@ -1,11 +1,11 @@ .\" Title: time.conf .\" Author: .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/> -.\" Date: 06/09/2006 +.\" Date: 06/21/2006 .\" Manual: Linux\-PAM Manual .\" Source: Linux\-PAM Manual .\" -.TH "TIME.CONF" "5" "06/09/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" +.TH "TIME.CONF" "5" "06/21/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -87,6 +87,6 @@ games ; * ; !waster ; Wd0000\-2400 | Wk1800\-0800 \fBpam_time\fR(8), \fBpam.d\fR(5), \fBpam\fR(8) -.SH "AUTHORS" +.SH "AUTHOR" .PP pam_time was written by Andrew G. Morgan <morgan@kernel.org>. diff --git a/modules/pam_time/time.conf.5.xml b/modules/pam_time/time.conf.5.xml index 08abb53b..224fda34 100644 --- a/modules/pam_time/time.conf.5.xml +++ b/modules/pam_time/time.conf.5.xml @@ -135,7 +135,7 @@ games ; * ; !waster ; Wd0000-2400 | Wk1800-0800 </refsect1> <refsect1 id="time.conf-author"> - <title>AUTHORS</title> + <title>AUTHOR</title> <para> pam_time was written by Andrew G. Morgan <morgan@kernel.org>. </para> |