setgid on mutt_dotlock?
Is mutt_dotlock supposed to be setgid (sorry Mikko, I meant setgid nor setuid in other message)? I changed it to 755 and I still get read-only permission on /var/spool/mail/vdanen which has -rw-rw permissions and is owned by vdanen.mail. I can't delete any messages in my inbox with the new mutt... help! -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net Freezer Burn BBS: telnet://bbs.freezer-burn.org . ICQ: 54924721 Webmaster for the Linux Portal Site Freezer Burn: http://www.freezer-burn.org Current Linux uptime: 1 days 2 hrs and 06 mins.
Re: setgid on mutt_dotlock?
On 2000-06-20 12:59:13 -0600, Vincent Danen wrote: Is mutt_dotlock supposed to be setgid (sorry Mikko, I meant setgid nor setuid in other message)? Yes. I changed it to 755 and I still get read-only permission on /var/spool/mail/vdanen which has -rw-rw permissions and is owned by vdanen.mail. The important thing are the permissions of the /var/spool/mail _directory_, not of the _file_ in that directory Dotlocking will create a file /var/spool/mail/vdanen.lock. In order to do this, mutt_dotlock needs write access to that directory, which is normally enabled by making mutt_dotlock setgid mail.
Re: setgid on mutt_dotlock?
I wrote a moment ago: Dotlocking will create a file /var/spool/mail/vdanen.lock. In order to do this, mutt_dotlock needs write access to that directory, which is normally enabled by making mutt_dotlock setgid mail. To illustrate things, here's an example from my system: % ls -ld /var/spool/mail /var/spool/mail/roessler /usr/local/bin/mutt_dotlock -rwxr-sr-x 1 root mail24231 Jun 20 10:32 /usr/local/bin/mutt_dotlock drwxrwsr-x 2 root mail 1024 Jun 8 16:56 /var/spool/mail -rw-rw 1 roessler mail0 Apr 18 16:19 /var/spool/mail/roessler (The spool file is actually unused since my mail gets delivered to a maildir folder in $HOME.)
Re: setgid on mutt_dotlock?
On Tue, Jun 20, 2000 at 10:43:52PM +0200, Thomas Roessler wrote: Dotlocking will create a file /var/spool/mail/vdanen.lock. In order to do this, mutt_dotlock needs write access to that directory, which is normally enabled by making mutt_dotlock setgid mail. To illustrate things, here's an example from my system: % ls -ld /var/spool/mail /var/spool/mail/roessler /usr/local/bin/mutt_dotlock -rwxr-sr-x 1 root mail24231 Jun 20 10:32 /usr/local/bin/mutt_dotlock drwxrwsr-x 2 root mail 1024 Jun 8 16:56 /var/spool/mail -rw-rw 1 roessler mail0 Apr 18 16:19 /var/spool/mail/roessler (The spool file is actually unused since my mail gets delivered to a maildir folder in $HOME.) Ok, that looks no different than mine. Mine *should* work then, right? I'm really confused as to why it isn't working then... =( -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net Freezer Burn BBS: telnet://bbs.freezer-burn.org . ICQ: 54924721 Webmaster for the Linux Portal Site Freezer Burn: http://www.freezer-burn.org Current Linux uptime: 1 days 4 hrs and 30 mins.
Re: setgid on mutt_dotlock?
On Tue, Jun 20, 2000 at 03:08:14PM -0500, Aaron Schrab wrote: Is mutt_dotlock supposed to be setgid (sorry Mikko, I meant setgid Yes, it needs to be setgid to the group that owns the mail spool directory. That's the whole point of it. Dotlocking in some configurations needs to be setgid, so it was moved out of mutt into a separate small program which is much easier to audit than all of mutt (including the libraries it uses). Ok... then the problem is somewhere else because when I use pine I can access the spool as well as the 1.0.1 version of mutt. -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net Freezer Burn BBS: telnet://bbs.freezer-burn.org . ICQ: 54924721 Webmaster for the Linux Portal Site Freezer Burn: http://www.freezer-burn.org Current Linux uptime: 1 days 4 hrs and 28 mins.
Re: setgid on mutt_dotlock?
On Tue, Jun 20, 2000 at 10:41:51PM +0200, Thomas Roessler wrote: I changed it to 755 and I still get read-only permission on /var/spool/mail/vdanen which has -rw-rw permissions and is owned by vdanen.mail. The important thing are the permissions of the /var/spool/mail _directory_, not of the _file_ in that directory Dotlocking will create a file /var/spool/mail/vdanen.lock. In order to do this, mutt_dotlock needs write access to that directory, which is normally enabled by making mutt_dotlock setgid mail. Ok, but the permissions seem to be fine for that directory... I really don't understand this: total 6 drwxr-xr-x 13 root root 265 May 26 16:28 ./ drwxr-xr-x 18 root root 357 Mar 13 10:53 ../ drwxr-xr-x2 root root 116 Jun 1 04:42 anacron/ drwx--3 daemon daemon 76 May 26 16:11 at/ drwx--2 root root 35 Apr 10 11:42 cron/ drwxrwxr-x3 root daemon 77 May 26 23:20 lpd/ drwxrwxr-x2 root mail 77 Jun 20 14:59 mail/ drwxr-xr-x2 root mail 35 Jun 20 15:20 mqueue/ drwxr-xr-x2 root root 35 Apr 13 11:37 rwho/ drwxrwxrwt2 root root 35 Apr 5 09:59 samba/ drwxr-x---2 squidsquid 35 May 2 02:12 squid/ drwxr-xr-x2 uucp root 35 Apr 3 03:51 uucp/ drwxr-xr-x2 uucp root 35 Apr 3 03:51 uucppublic/ -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net Freezer Burn BBS: telnet://bbs.freezer-burn.org . ICQ: 54924721 Webmaster for the Linux Portal Site Freezer Burn: http://www.freezer-burn.org Current Linux uptime: 1 days 4 hrs and 29 mins.
