Bug 5090 – proble with umask

Bug 5090 - proble with umask

Summary:	proble with umask

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	setup (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-09-12 14:13 EDT by mal
Modified:	2014-03-16 22:09 EDT (History)
CC List:	1 user (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description mal 1999-09-12 14:13:14 EDT

Hi,
there is a problem with
/etc/profile
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
su
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.
Vladislav

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.