Bug 201008

Summary: Request for administrator-defined list separator parameter for pam_access.so
Product: Red Hat Enterprise Linux 4 Reporter: Jose Plans <jplans>
Component: pamAssignee: Tomas Mraz <tmraz>
Status: CLOSED ERRATA QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: srevivo, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-0300 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1334138 (view as bug list) Environment:
Last Closed: 2007-05-01 17:24:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1334138    

Description Jose Plans 2006-08-02 08:52:21 UTC
+++ This bug was initially created as a clone of Bug #132135 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
I am using Samba's winbindd and associated nsswitch modules to
authenticate users against a Windows 2000 domain.  I would like to
restrict access to certain services (like an SSH or console login)
using the pam_access module.  The default configuration file for this
module is /etc/security/access.conf, and it allows me to specify a
list of groups or users who should or should not be given access.

Unfortunately, pam_access interprets spaces in a list of groups or
usernames as a separator, and Windows domains tend to have a lot of
group names with spaces.  The default built-in group "Domain Users" is
a prime example.

The module already supports a parameter that allows defining a
different separator between field names.  (The default is a ':', as in
+-:usersgroups:hosts.)  It would be nice if the administrator could
also specify a different separator to use between each group/user and
each hostname.  The default of ' \t,' is hard-coded.  If this were the
case, then this line in my access.conf would do what I wanted:

+:Domain Admins,root:ALL
-:ALL:ALL

(Currently, the above would look for users who are in group "Domain"
or "Admins" but not "Domain Admins.")

Version-Release number of selected component (if applicable):
pam-0.77-15

How reproducible:
Always

Steps to Reproduce:
1.  Configure Winbind to retrieve users and groups from an existing
Windows domain.
2.  Configure the system (nsswitch and PAM) to use the winbind modules
for authentication and name resolution.
3.  Add the line "account pam_access.so" to your PAM service
configuration file (let's use /etc/pam.d/sshd for this case; you will
also have to specify UsePAM=yes in /etc/ssh/sshd_config).
4.  Configure /etc/security/access.conf to disallow the group name
with spaces in it:
+:Domain Admins,root:ALL
-:ALL:ALL
5.  Attempt a login with the service and note that PAM rejects the login.

-- Additional comment from rshaffer on 2004-09-08 22:18 EST --
Created an attachment (id=103621)
Patch to enable requested feature

Adds a new parameter, listsep, to the module.

Example (/etc/pam.d/sshd or other):

account pam_access listsep=,

Example (/etc/security/access.conf):

+:Domain Admins,root:ALL
-:ALL:ALL

-- Additional comment from tmraz on 2005-05-27 06:34 EST --
The patch was accepted upstream so it will be pulled in the next upgrade of pam
package from upstream to Fedora Core development.

Comment 1 RHEL Program Management 2006-08-18 14:50:04 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 2 Jay Turner 2006-08-29 01:12:40 UTC
QE ack for 4.5.

Comment 9 Red Hat Bugzilla 2007-05-01 17:24:08 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0300.html