Krzysztof Halasa <khc@xxxxxxxxx> writes: > Junio C Hamano <junkio@xxxxxxx> writes: > >> If the archive is made with 022, that would >> break expectation of users whose umask is 002 (a sane value in >> modern "own" group setups). > > What exactly do they expect from 002? That root group will be able > to write to the files? It is more like "no suspicious individual would not be able to write to them". You could always tell tar to honor your umask while extracting as root and have 022 or a tighter umask if you have somebody untrustworthy in your 'root' group. And in mordern setup, umask 002 makes tons of sense. My primary group is 'junio' in modern setup, but I belong to secondary groups like 'git' and 'mix' that are shared with other people who work on 'git' and 'mix' projects. umask 002 is the natural thing to use from log-in and never change. My home directory is owned by junio.junio and has mode 2775. Only I can create a new file or a directory there, and result of doing so is owned by junio.junio and has 0664 or 0775 which means only I can write to it. A directory used by 'git' project is owned by <somebody>.git where that <somebody> is from the git group and has mode 2775. Only the project members of 'git', who shared the 'git' group with me, can create a new file or a directory there, and result of doing so is owned by <user>.git where <user> is the project member who is doing so, and has 0664 or 0775 which means only the project members of 'git' can write to it. - 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