Bug 1902166
| Summary: | bashrc sets hardcoded umask | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pavel Zhukov <pzhukov> |
| Component: | setup | Assignee: | Martin Osvald 🛹 <mosvald> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | davide.corrado, eurbah, karsten, kdudka, marcosfrm, mattdm, mosvald, ovasik, pknirsch, pzhukov, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | setup-2.14.1-1.fc36 setup-2.14.1-1.fc35 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-07-26 16:13:33 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: | 2062601 | ||
|
Description
Pavel Zhukov
2020-11-27 07:45:01 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34. There's a related conversation here https://ask.fedoraproject.org/t/default-umask-value/18648 The current configuration does seem pretty arbitrary to me, especially the distinction between login and non-login shells. I note that there's a lot of back-and-forth history in the changelog (see for example #217523). Personal opinion: that shared-login-server filesystem-permissions-based-collaboration use case is a pretty rare one these days, and systems where that's still important can explicitly configure for that if needed. And I also note that the check there for UID > 199 is ... maybe a decade obsolete? Let's just take this out? Less code is better, right? :) *** Bug 1940375 has been marked as a duplicate of this bug. *** I'm copying over a comment from the other bug so this doesn't get lost:
> please change /etc/bashrc to only touch umask if it is 000, and leave the existing setting otherwise.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36. This bug is still present in package setup 2.13.10-1.fc36
Workarounds :
If you are sudoer, inside '/etc/bashrc', you can replace 'umask 002' by 'true # umask 002 now managed by pam_umask'
If you are not sudoer, you can add following lines at the end of ~/.bashrc :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
Would this be an acceptable solution for the parties involved? https://pagure.io/setup/pull-request/36 https://pagure.io/fork/mosvald/setup/c/206d4afccaec7b20caafa79d6b005ec681e2551b Works for me. Thanks! FEDORA-2022-984296572a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-984296572a FEDORA-2022-4b663b23a9 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-4b663b23a9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4b663b23a9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-984296572a has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-984296572a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-984296572a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-984296572a has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-4b663b23a9 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |