[Rpm-maint] Bug: rpm should set a fixed umask of 0022 before running pre-/post scripts

[devzero2000]

If you like an opinion as sysadmin, i agreed with Michael. I don't think it
is rpm job to change
what it is the default umask setting on the system or the sysadmin in
particolar. If I want different, well, someone can always to define in the
desidered way in the spec file for safety and portablity. If the root umask
is wrong or truly restrictive there is nothing to do to stop it: for example
it could be create /etc/hosts 400 and the like. RPM file perhaps had sound
perms with the fix  but what about the other config files, or other item ?

Elia



On Wed, May 28, 2008 at 1:37 PM, Panu Matilainen <pmatilai at redhat.com>
wrote:

> On Wed, 28 May 2008, Michael Schroeder wrote:
>
>  On Wed, May 28, 2008 at 01:03:13PM +0300, Panu Matilainen wrote:
>>
>>> Rpm 4.4.2.3 and newer sets umask to 0022 on initialization, so it is
>>> already "fixed" upstream. Not that 0022 is a magic universally
>>> absolutely correct value for umask, it's just what most things
>>> (scriptlets
>>> notably) expect.
>>>
>>
>> Actually I do not agree with the fix. At least SUSE's scriptlets
>> tend to restart daemons if an update is installed, with this
>> change the new processes will have an umask that is different
>> from the system's configuration.
>>
>
> Note the quotes around "fixed"... Previously rpm and anything (re)started
> from it was at the mercy of root user's umask, nothing guarantees that to be
> the same as "system configuration" (ie what's in effect at boot time)
> either. The new behavior ensures some predictability, not much more.
>
>        - Panu -
>
> _______________________________________________
> Rpm-maint mailing list
> Rpm-maint at lists.rpm.org
> https://lists.rpm.org/mailman/listinfo/rpm-maint
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rpm.org/pipermail/rpm-maint/attachments/20080528/6a757636/attachment-0001.htm