Re: Default "tar" umask..

From: Junio C Hamano <junkio@cox.net>
Date: Jan 5, 2007, 21:03 UTC
Message-ID: <7vzm8xdw3t.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <459EB78B.60000@lsrfire.ath.cx>

René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:

Show 12 quoted lines

> Junio C Hamano schrieb:
>> ...
>> Having said that, I do not see much reason for anybody to want to
>> extract any material that is worth to be placed under version control
>> in a way that is world-writable, so I do not mind having 002 as the
>> default, but I feel that group-writability should be kept under
>> control of the umask of end users who know what they are doing.
>
> Yes, using 002 is tempting.  But it's got the same "looseness" problems
> as 000, only on a smaller scaler: there are certainly situations where a
> user doesn't want to share write permissions with all the members of her
> current group.  If we change the default, let's go all the way to 022.

I don't think the above argument makes much sense -- it does not explain why you do not go "all the way" to 077.

On the other hand, I can explain 002 fairly easily and consistently. This matters only for users who can become root and does not know or care about implied -p, and the group root belongs to had better not contain any suspicious user, so leaving group open does not hurt. 022 actively hurts sane usage (i.e. work always with a sane umask and extract as non root users) while 002 does not.

> Admittedly, that doesn't help users who download from a "022" project,
> but really want something looser.  I think it's more important to
> avoid violating the expectations of all those who freak out at 0666
> permission modes attached to their freshly downloaded files, though.

Exactly, and that is why I think 002 is much saner.