Re: problems with "make install" directory permissions
Karl Berry wrote: > https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html > > I can understand increasing permissions to allow +rx on installation > directories, but why force 755, thus disallowing group writability? > I've never understood this forcing of 755. As the one who originally brought this up on bug-bison, I was only referring to newly created install directories. Existing directories should not have their mode changed, IMHO. One can certainly argue for g+w. Since the directories are newly created, one cannot look at the existing mode to decide whether to do this. One could use the umask for that bit only, though this may be a bit unintuitive. So a typical umask of 022 or 077 would result in 755, but a umask of 002 or 007 would result in 775. Regards, Frank
Re: problems with "make install" directory permissions
On Mon, Jul 27, 2020 at 3:03 PM Paul Eggert wrote: > > On 7/27/20 2:24 PM, Karl Berry wrote: > > https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html > > > > I can understand increasing permissions to allow +rx on installation > > directories, but why force 755, thus disallowing group writability? > > I've never understood this forcing of 755. > > I expect it was by analogy with regular files, where are already forced to use > the equivalent of umask 22 when being installed. > > This could have been a decision I made years ago when modifying GNU 'install' > - > I've forgotten the details. (No doubt it was a good decision at the time. :-) >From what I recall, we deliberately avoid making installed things group-writable because that would induce a security risk in installations where more than one user is in the same default group. If I install in such an environment (and don't override the group), I don't want a peer to be able to modify what I've just installed.
Re: problems with "make install" directory permissions
On 7/27/20 2:24 PM, Karl Berry wrote: https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html I can understand increasing permissions to allow +rx on installation directories, but why force 755, thus disallowing group writability? I've never understood this forcing of 755. I expect it was by analogy with regular files, where are already forced to use the equivalent of umask 22 when being installed. This could have been a decision I made years ago when modifying GNU 'install' - I've forgotten the details. (No doubt it was a good decision at the time. :-)
Re: problems with "make install" directory permissions
https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html I can understand increasing permissions to allow +rx on installation directories, but why force 755, thus disallowing group writability? I've never understood this forcing of 755. I don't think Zack plans to release a new Automake. Jim and I released automake-1.16.2 in March this year. We could make another release, but it seems you have already dealt with it sufficiently. As far as I know, there are no huge outstanding problems in automake. I have been slowly trying to look at the backlog of bugs (since no one else was, for years) and at least apply patches that have been submitted. Tons remain. Of course other active contributors would be most welcome. --thanks, karl.
