Bug 1300700
| Summary: | screen utility resets umask | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | dpecka |
| Component: | screen | Assignee: | Vaclav Dolezal <vdolezal> |
| Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | dpecka, ekirby, jkejda, ovasik |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-15 14:13:39 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1420851, 1465925, 1473612 | ||
|
Description
dpecka
2016-01-21 13:46:47 UTC
I'd like to additionally add the following: my standpoint is: if screen does like that (is affected by this) non-transparently what else is covertly affected by this ? Once you start in el hardening the security in umask area, you are forced to drop defaults and deploy relatively lot of changes .. Generally said, I don't expect that this will change in current el7 release because of changing policy but I hope, that it will leak to fedora and afterwards to future rhel releases ... Hello again, one more findings, this umask comes from /etc/bashrc (the one from screen) ... in regard to bug 1283670 I even overlooked, that umask is additionally in /etc/bashrc also ... But it's still valid, that you should be able to reproduce it with el6/7 defaults as well as with umask settings moved to pam .. Did another tests, I've put my umask settings in el7 to ~/.profile ... doesn't work either because of .bashrc from SKEL doing (after .profile): if [ -f /etc/bashrc ]; then . /etc/bashrc fi This is ridiculous to re-write umask on N places during the shell invocation. I can unserstand, that umask is in el7 supposed to be set just from ~/.bashrc (not from ~/.profile and not from PAM) but I'd consider this design as broken. Regards, daniel May I ask you for explanation, why do you think, this issue can be resolved by screen update? (regards to bug 1283670) From my point of view it is correct behavior due your umask setting is valid for your current shell session only. By calling screen command (or bash etc.) you create new shell session with default umask settings. Assigning to new maintainer. Hello. Since screen doesn't manipulate its umask (see below), I don't see any problem in screen. umask is set inside bash by sourcing its rc files. Regards, Václav Doležal --- $ umask 0002 $ umask 0077 $ umask 0077 $ screen screen 0:bash$ umask 0002 (screen cmdline): screen bash --noprofile --norc screen 1:bash$ umask 0077 (another term)# cat /proc/`pidof SCREEN`/status |grep Umask Umask: 0077 Since screen doesn't touch its umask (or umasks of its children) and I don't see any thing that screen can do better in this regard, I'm closing this bug. If you disagree with this reasoning, please elaborate on it. Regards, Václav Doležal The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |