[Bug 1731626] [NEW] Bash disregards umask: All new files are created world writeable (Posix default)
Karl Kastner
kastner.karl at gmail.com
Sat Nov 11 13:38:39 UTC 2017
Public bug reported:
umask is set in my system set to 022. This is also what umask on the
bash spits out. However, new files are always created with permission
666 and new directories with 777, thus world writeable, as is the posix
default. When I explicitely set umask in my .bashrc, for example to 002,
then the values reported by umask change accordingly, but new files are
still created with mask 666. It is not particular to the gnome or X
environment, as it also hasppens on the terminal as well. Strangely,
this does not necessarily happen to files created deep in the directory
structure, but always to files in the home directory.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: bash 4.4-2ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Nov 11 14:22:28 2017
InstallationDate: Installed on 2015-11-05 (737 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: bash
UpgradeStatus: Upgraded to zesty on 2017-10-16 (26 days ago)
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug zesty
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1731626
Title:
Bash disregards umask: All new files are created world writeable
(Posix default)
Status in bash package in Ubuntu:
New
Bug description:
umask is set in my system set to 022. This is also what umask on the
bash spits out. However, new files are always created with permission
666 and new directories with 777, thus world writeable, as is the
posix default. When I explicitely set umask in my .bashrc, for example
to 002, then the values reported by umask change accordingly, but new
files are still created with mask 666. It is not particular to the
gnome or X environment, as it also hasppens on the terminal as well.
Strangely, this does not necessarily happen to files created deep in
the directory structure, but always to files in the home directory.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: bash 4.4-2ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Nov 11 14:22:28 2017
InstallationDate: Installed on 2015-11-05 (737 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: bash
UpgradeStatus: Upgraded to zesty on 2017-10-16 (26 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1731626/+subscriptions
More information about the foundations-bugs
mailing list