Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1025065

Summary: Authconfig does not specify args for pam_mkhomedir which results in umask=0022 and world-readable home directories.
Product: Red Hat Enterprise Linux 6 Reporter: John Conroy <jconroy>
Component: authconfigAssignee: Tomas Mraz <tmraz>
Status: CLOSED ERRATA QA Contact: David Spurek <dspurek>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6CC: dspurek, ebenes, ian, tmraz
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: authconfig-6.1.12-14.el6 Doc Type: Bug Fix
Doc Text:
Cause: The default umask when creating home directories with pam_mkhomedir is 0022. Consequence: The home directories created with pam_mkhomedir were world readable. Fix: Use umask=0077 option with pam_mkhomedir by default. Result: The home directories newly created by pam_mkhomedir are no longer world readable.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 07:44:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Conroy 2013-10-30 22:40:33 UTC
Description of problem:
By default, authconfig does not specify args for pam_mkhomedir (or pam_oddjob_mkhomedir) which results in umask=0022 and world-readable home directories.

Version-Release number of selected component (if applicable):
authconfig-6.1.12-13.el6

How reproducible:
Always

Steps to Reproduce:
1.  authconfig --enablemkhomedir --updateall
2.  Check the PAM config files in /etc/pam.d
3.

Actual results:
No arguments are supplied, resulting in a UMASK of 0022 for home directories making them world-readable by default.

Expected results:
Something along the lines of "skel=/etc/skel/ umask=0077", though skel is supposed to be defaulted to /etc/skel and should be unecessary.

Additional info:
Should probably update authinfo.py to supply a more sane default UMASK to the pam_mkhomedir plugin or allow the args to be specified on the command line and saved in /etc/sysconfig/authconfig...or both.  :)

self.mkhomedirArgs = "skel=/etc/skel/ umask=0077"

Comment 3 Tomas Mraz 2014-03-26 09:51:29 UTC
We would just add umask=0077 to the initial arguments of pam_mkhomedir/pam_oddjob_mkhomedir if enabled with --enablemkhomedir.

Comment 7 errata-xmlrpc 2014-10-14 07:44:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1558.html