Date: Tue, 14 Sep 2010 11:22:49 -0700 From: Chuck Swiger <cswiger@mac.com> To: doug@safeport.com Cc: Polytropon <freebsd@edvax.de>, freebsd-questions@freebsd.org Subject: Re: unix permissions questions Message-ID: <270B9E77-D1B2-43AC-98EC-EEC9F8CE840A@mac.com> In-Reply-To: <alpine.BSF.2.00.1009141414080.26109@oceanpt.safeport.com> References: <alpine.BSF.2.00.1009141324020.26109@oceanpt.safeport.com> <20100914200116.23a34732.freebsd@edvax.de> <B3697A31-7525-42D9-BAD7-93FCADF6F960@mac.com> <alpine.BSF.2.00.1009141414080.26109@oceanpt.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 14, 2010, at 11:16 AM, doug@safeport.com wrote: >> A bit of experimentation suggests that "chmod 7500 .procmail" are the permissions involved, which are silly. No group permissions enabled means setgid is meaningless, and I don't see any value for using the sticky bit here, either. Try using 0500, 0700, or maybe 4500/4700 instead. > > thanks all - the context of this: the users involved do not know what the chmod command is much less its syntax and I did not do this. What I was going for was could this be a procmail bug or perhaps something more alarming (to me as a sysadmin). The permissions here are unexpected. procmail cares about clearing group and other permissions-- unless GROUP_PER_USER is set (cf http://partmaps.org/era/procmail/mini-faq.html#group-writable), which usually would be appropriate for FreeBSD since it encourages all userids to also have a corresponding groupid. Regards, -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?270B9E77-D1B2-43AC-98EC-EEC9F8CE840A>