** Changed in: procmail (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: procmail (Ubuntu)
Assignee: Kees Cook (kees) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/4
Unfortunately not. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/407459
Title:
Procmail opens $HOME/.procmailrc before dropping setuid permissions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
@Kees, did you ever hear anything back from upstream?
** Changed in: procmail (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: procmail (Ubuntu)
Assignee: (unassigned) => Kees Cook (kees)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah, good point about the open() side-effects. I have emailed upstream,
so hopefully they can provide some ideas on the best way to handle this.
** Changed in: procmail (Ubuntu)
Status: New => Confirmed
** Changed in: procmail (Ubuntu)
Importance: Undecided => Low
--
Procmail opens $H
** Changed in: procmail (Ubuntu)
Status: Invalid => New
--
Procmail opens $HOME/.procmailrc before dropping setuid permissions
https://bugs.launchpad.net/bugs/407459
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Even if procmail closes and reopens the file later as non-root,
there are still two problems here. First, procmail has opened
(and closed) a file with root permissions. There are 'files'
where merely opening (and closing) them have side effects;
for example, pointing $HOME/.procmailrc at a rewindab
Thanks for this report! As it turns out, this is just procmail
attempting to work around the exact issue (strict NFS). If it were to
actually open the rc file as root, it would close it and reopen after
dropping privileges:
/*
* if we happen to be still running as root, and the rcfile
*
