Bug 632 – 'Defaults umask=' directive not working anymore

Bug 632 - 'Defaults umask=' directive not working anymore


Summary:	'Defaults umask=' directive not working anymore

Status:	RESOLVED FIXED

Product:	Sudo
Classification:	Unclassified
Component:	Sudo
Version:	1.8.9
Hardware:	PC Linux

Importance:	low normal
Assigned To:	Todd C. Miller

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-01-30 12:32 MST by Maxime ROSSINI
Modified:	2014-02-04 10:23 MST (History)
CC List:	0 users

See Also:

Attachments
Fix for sudoers umask parsing (602 bytes, patch) 2014-01-30 13:08 MST, Todd C. Miller	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

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

Description Maxime ROSSINI 2014-01-30 12:32:06 MST

After installing the recent 1.8.9p4 update (from 1.8.8), I get the following warning message each time I run the sudo command, and before the password prompt:

sudo: value `0007' is invalid for option `umask'
sudo: value `0022' is invalid for option `umask'

The warnings are generated by the folowing lines in my sudoers file '/etc/sudoers.d/umasks':

#UMASK is not unioned with the one set in the PAM module
Defaults        umask_override
#Default UMASK is 007 for non-root users
Defaults        umask=0007
#Root UMASK is 022, to overcome permission problems when installing packages
Defaults>root   umask=0022

It appears the files created under sudo are indeed no longer using the specified umask, the umask directive in the config file is ignored.

Comment 1 Todd C. Miller 2014-01-30 13:08:31 MST

Created attachment 394 [details]
Fix for sudoers umask parsing

Please try the attached patch.

Comment 2 Todd C. Miller 2014-02-04 10:23:33 MST

Fixed in sudo 1.8.9p5, available now.