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 2089437 - missing umask in the /etc/profile
Summary: missing umask in the /etc/profile
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: Documentation
Version: 9.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Mariya Pershina
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-23 16:45 UTC by justsomeone
Modified: 2022-06-20 06:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-16 12:44:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-123027 0 None None None 2022-05-23 16:57:36 UTC

Description justsomeone 2022-05-23 16:45:43 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_basic_system_settings/assembly_managing-the-umask_configuring-basic-system-settings#displaying-the-default-umask_assembly_managing-the-umask


Section Number and Name: 

25.2. Displaying the default bash umask

Describe the issue: 

in the Procedure section 

To display the default bash umask for the login shell, use: 

grep umask /etc/profile

the file /etc/profile does not have any umask i tried with rhel 9 beta 5 and i asked someone who has rhel 9 release version and he confirm the file does not have umask also


Suggestions for improvement: 

i am not sure if it bug of the os or i am missing something (i am just starting to learn rhel so i could miss something)
or is there some use cases that make that file does not have the umask for some reason

if the issue with the documentations then

this section 

25.6. Changing the default umask for the login shell

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_basic_system_settings/assembly_managing-the-umask_configuring-basic-system-settings#changing-default-umask-login-shell_assembly_managing-the-umask

will need to be updated as well

and for this section

25.8. Setting default UMASK for newly created home directories

/etc/login.defs does not have this section

# The permission mask is initialized to this value. If not specified,
# the permission mask will be initialized to 022.
UMASK 077

i guess it should be

# Default initial "umask" value used by login(1) on non-PAM enabled systems.
# Default "umask" value for pam_umask(8) on PAM enabled systems.
# UMASK is also used by useradd(8) and newusers(8) to set the mode for new
# home directories if HOME_MODE is not set.
# 022 is the default value, but 027, or even 077, could be considered
# for increased privacy. There is no One True Answer here: each sysadmin
# must make up their mind.
UMASK		022

or you mean the HOME_MODE

# HOME_MODE is used by useradd(8) and newusers(8) to set the mode for new
# home directories.
# If HOME_MODE is not set, the value of UMASK is used to create the mode.
HOME_MODE	0700



thanks for your time and help and have a nice day :)

Comment 9 justsomeone 2022-06-16 13:33:56 UTC
thanks @mpershin and for the whole team


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