Relevant BUGIDs: 547051, 547521

Purpose of commit: bugfixes

Commit summary:
---------------
Both of these fixes inspired by use with X based services.
The first makes a TTY of the form hostname:0 work (if you specify a different
separator with the module argument "fieldsep=".
The second treats "" for a RHOST the same way it would treat a NULL value.

1 files changed, 13 insertions, 4 deletions

diff --git a/doc/modules/pam_access.sgml b/doc/modules/pam_access.sgml
index 00c7ea16..8a910d13 100644
--- a/doc/modules/pam_access.sgml
+++ b/doc/modules/pam_access.sgml
@@ -22,8 +22,6 @@ Alexei Nogin <alexei@nogin.dnttm.ru>
 
 <tag><bf>Maintainer:</bf></tag>
 	
-Author
-
 <tag><bf>Management groups provided:</bf></tag>
 
 account
@@ -59,7 +57,8 @@ Provides logdaemon style login access control.
 
 <tag><bf>Recognized arguments:</bf></tag>
 
-<tt>accessfile=<it>/path/to/file.conf</it></tt>
+<tt>accessfile=<it>/path/to/file.conf</it></tt>;
+<tt>fieldsep=<it>separators</it></tt>
 
 <tag><bf>Description:</bf></tag>
 
@@ -79,7 +78,17 @@ arguments:
 indicate an alternative <em/access/ configuration file to override 
 the default. This can be useful when different services need different 
 access lists. 
- 
+
+<item><tt>fieldsep=<it>separators</it></tt> -
+this option modifies the field separator character that
+<tt/pam_access/ will recognize when parsing the access configuration
+file. For example: <tt>fieldsep=|</tt> will cause the default `:'
+character to be treated as part of a field value and `|' becomes the
+field separator. Doing this is useful in conjuction with a system that
+wants to use pam_access with X based applications, since the
+<tt/PAM_TTY/ item is likely to be of the form "hostname:0" which
+includes a `:' character in its value.
+
 </itemize> 
 
 <tag><bf>Examples/suggested usage:</bf></tag>