Re: What happened to umask?

2022-05-23 Thread Pavel Zhukov
Owen Taylor writes: > For years, Red Hat Linux / Fedora systems have had a umask of 0002 for > regular users as part of the "user private group" scheme [*]. Basically the > idea is that > you can set a directory group-sticky and use it as a common work area for a > group of users. > > A chang

Re: What happened to umask?

2022-05-22 Thread Stephen Smoogen
On Sun, 22 May 2022 at 06:52, Zbigniew Jędrzejewski-Szmek wrote: > On Sun, May 22, 2022 at 10:30:48AM +0200, Vitaly Zaitsev via devel wrote: > > On 21/05/2022 20:57, Demi Marie Obenour wrote: > > > I think Fedora should go use an 0077 umask for this reason. > > > > Fedora is a general purpose dis

Re: What happened to umask?

2022-05-22 Thread Zbigniew Jędrzejewski-Szmek
On Sun, May 22, 2022 at 10:30:48AM +0200, Vitaly Zaitsev via devel wrote: > On 21/05/2022 20:57, Demi Marie Obenour wrote: > > I think Fedora should go use an 0077 umask for this reason. > > Fedora is a general purpose distribution, so umask 0077 will create more > problems than it solves. > > Al

Re: What happened to umask?

2022-05-22 Thread Vitaly Zaitsev via devel
On 21/05/2022 03:00, Neal Gompa wrote: I think we should complete the transition to 0022 umask. +1 to 0022. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: What happened to umask?

2022-05-22 Thread Vitaly Zaitsev via devel
On 21/05/2022 20:57, Demi Marie Obenour wrote: I think Fedora should go use an 0077 umask for this reason. Fedora is a general purpose distribution, so umask 0077 will create more problems than it solves. Also by default the /home directories have 0700 chmod so no one but the owner can acce

Re: What happened to umask?

2022-05-21 Thread Demi Marie Obenour
On 5/20/22 21:32, Nico Kadel-Garcia wrote: > On Fri, May 20, 2022 at 9:08 PM Neal Gompa wrote: >> >> On Fri, May 20, 2022 at 8:13 PM Owen Taylor wrote: >>> >>> For years, Red Hat Linux / Fedora systems have had a umask of 0002 for >>> regular users as part of the "user private group" scheme [*].

Re: What happened to umask?

2022-05-21 Thread Ron Yorston
Owen, Thanks for explaining the situation with umask. I'd noticed the discrepancy between login/non-login shells and wondered what was going on. >It seems like we need to do one of two things: > > - Go back to the old behavior, maybe by using the usergroups option to >pam_umask and removing the

Re: What happened to umask?

2022-05-20 Thread Nico Kadel-Garcia
On Fri, May 20, 2022 at 9:08 PM Neal Gompa wrote: > > On Fri, May 20, 2022 at 8:13 PM Owen Taylor wrote: > > > > For years, Red Hat Linux / Fedora systems have had a umask of 0002 for > > regular users as part of the "user private group" scheme [*]. Basically the > > idea is that you can set a

Re: What happened to umask?

2022-05-20 Thread Neal Gompa
On Fri, May 20, 2022 at 8:13 PM Owen Taylor wrote: > > For years, Red Hat Linux / Fedora systems have had a umask of 0002 for > regular users as part of the "user private group" scheme [*]. Basically the > idea is that you can set a directory group-sticky and use it as a common work > area for

What happened to umask?

2022-05-20 Thread Owen Taylor
For years, Red Hat Linux / Fedora systems have had a umask of 0002 for regular users as part of the "user private group" scheme [*]. Basically the idea is that you can set a directory group-sticky and use it as a common work area for a group of users. A change a couple of years ago seems to have p