Bug 5090 - proble with umask
proble with umask
Product: Red Hat Linux
Classification: Retired
Component: setup (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 1999-09-12 14:13 EDT by mal
Modified: 2014-03-16 22:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-12-08 16:13:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description mal 1999-09-12 14:13:14 EDT
there is a problem with
in setup-1.9.2-1 package.
Specifically, when
selecting what umask to set
002 or 022
it checkes for iser id and group id.
If a process has effective user id or effective group id
different a wrong pernission may be set.
(for example if a user does
root will get 002 umask)
A fix to this problem is to test effective UID and effective
GID, not UID and GID as it is now.
Comment 1 Bill Nottingham 1999-12-08 16:13:59 EST
Um, id already does that.

If you just invoke 'su', it's not a login shell, so
/etc/profile is never read, so the umask is inherited
from the parent process.

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