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.
DescriptionAshish Kumar Singh
2020-05-09 13:16:17 UTC
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
Below is a simple reproduction showing umask difference regression using centos docker images. same holds true for redhat based images.
ashish@BLRMAC57-4 ~ % docker run centos:7 umask
0022
ashish@BLRMAC57-4 ~ % docker run centos:8 umask
0022
ashish@BLRMAC57-4 ~ % docker run centos:7 su root -c umask
0022
ashish@BLRMAC57-4 ~ % docker run centos:8 su root -c umask
0077
ashish@BLRMAC57-4 ~ %
Actual results:
Umask in centos 8 when a command is run under su is 0077
Expected results:
it should be 0022
Additional info:
This breaks defaults permission of files in 8.x series of os vs 7.x series when a program impersonates a user to write a file.
(In reply to Ashish Kumar Singh from comment #0)
> Below is a simple reproduction showing umask difference regression using
> centos docker images. same holds true for redhat based images.
>
> ashish@BLRMAC57-4 ~ % docker run centos:7 umask
> 0022
> ashish@BLRMAC57-4 ~ % docker run centos:8 umask
> 0022
> ashish@BLRMAC57-4 ~ % docker run centos:7 su root -c umask
> 0022
> ashish@BLRMAC57-4 ~ % docker run centos:8 su root -c umask
> 0077
it's set from /etc/login.defs reassigned to shadow-utils for further investigation