Bug 1801569

Summary:	Do not reset umask in /etc/profile
Product:	[Fedora] Fedora	Reporter:	Pavel Zhukov <pzhukov>
Component:	setup	Assignee:	Pavel Zhukov <pzhukov>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	karsten, kdudka, ovasik, pknirsch
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-11 15:40:52 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 Pavel Zhukov 2020-02-11 08:59:42 UTC

Description of problem:
Currently umask is changed in /etc/profile to hardcoded value 022 (or 002) and this override umask which has been set with pam module which is confusing

Version-Release number of selected component (if applicable):
setup-2.13.6-1.fc32.noarch

How reproducible:
100%

Steps to Reproduce:
1. change umask in login.defs
2. relogin
3. check umask set

Actual results:
# umask
0022

Expected results:
# umask
-- value set in login.defs

Additional info:

See https://bugzilla.redhat.com/show_bug.cgi?id=1283670

Comment 4 Kamil Dudka 2020-02-11 14:51:49 UTC

Is this a duplicate of bug #1722387?

Comment 5 Pavel Zhukov 2020-02-11 15:40:52 UTC

(In reply to Kamil Dudka from comment #4)
> Is this a duplicate of bug #1722387?

Whooops. Yes, it is.
Thank you for checking!

*** This bug has been marked as a duplicate of bug 1722387 ***