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 961348 - /etc/bashrc sets umask based on wrong user number range
Summary: /etc/bashrc sets umask based on wrong user number range
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: setup
Version: 6.4
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Ondrej Vasik
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-09 13:04 UTC by Alain D D Williams
Modified: 2013-05-09 18:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-09 18:49:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alain D D Williams 2013-05-09 13:04:30 UTC
Description of problem:

/etc/bashrc contains:

    # By default, we want umask to get set. This sets it for non-login shell.
    # Current threshold for system reserved uid/gids is 200
    # You could check uidgid reservation validity in
    # /usr/share/doc/setup-*/uidgid file
    if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
       umask 007
    else
       umask 027
    fi


However /etc/login.defs contains:

# Min/max values for automatic uid selection in useradd
#
UID_MIN			  500

Ie daemon/... users are created with usernumbers greater than 200. Eg uuidd has the usernumber 499.

Comment 2 Ondrej Vasik 2013-05-09 18:49:42 UTC
It is intentional, although it seems to be strange. Before, when the static ID limit was 100, this number was 99, therefore it was increased to 199, as the limit was increased to 200. This is old behaviour - different umask for static system ids and different for the others. 

TBH, I don't know why it was done that way, it is very old stuff. I tend to close it WONTFIX for RHEL. We are actually discussing exactly same thing in Fedora, in #957852. I want to investigate the reasons behind different behaviour for static and dynamic range of system ids before doing any change there.

Comment 3 Ondrej Vasik 2013-05-09 18:51:19 UTC
(please note that UID_MIN is the border of user ids, not the static ids... this is tracked by SYS_UID_MIN in later Fedora, but not in RHEL-6 afaik.


Note You need to log in before you can comment on or make changes to this bug.