On Fri, 5 Jan 2007, Junio C Hamano wrote: > > > > 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. I really think that 022 is the right choice, for a very simple reason: peoples expectations. It's just _common_. > On the other hand, I can explain 002 fairly easily and > consistently. No you can't. 002 makes no sense at all in a very common old-fashioned setup with a "user" group. Maybe I'm old, and these days most setups seem to give people their own group (so I'm "torvalds:torvalds" on all the machines I have access to), but it used to be _very_ common to have just a "user" group that all normal users were part of (or have the default gid depend on something like which department you are in). In that situation, 002 is really effectively no different at all from 000. Which is why 022 is the historical default for umask. 022 really is very easy to explain: "readability (and executability) is a lot less dangerous than writability, and by default we only give writability to the user". That's why we _don't_ commonly have 066 or 077 as the umask, and also why 002 is the default umask ONLY on systems where users have their own individual groups by default. Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html