http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5365

           Summary: spamd child falling back to nobody attempts to use
                    previous user's database
           Product: Spamassassin
           Version: 3.1.7
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamc/spamd
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


incoming message processed for user 'xxx':

Mar  4 16:33:53 hostname spamd[5227]: spamd: connection from localhost
[127.0.0.1] at port 39629 
Mar  4 16:33:53 hostname spamd[5227]: spamd: setuid to xxx succeeded 
Mar  4 16:33:53 hostname spamd[5227]: spamd: processing message <[EMAIL 
PROTECTED]> for xxx:1677 
Mar  4 16:33:55 hostname spamd[5227]: spamd: clean message (-0.1/5.0) for
xxx:1677 in 1.3 seconds, 4360 bytes. 
Mar  4 16:33:55 hostname spamd[5227]: spamd: result: ...

then later on for a user that doesn't exist:

Mar  4 16:39:09 hostname spamd[5227]: spamd: connection from localhost
[127.0.0.1] at port 39791 
Mar  4 16:39:09 hostname spamd[5227]: spamd: handle_user unable to find user:
'test' 
Mar  4 16:39:09 hostname spamd[5227]: spamd: still running as root: user not
specified with -u, not found, or set to root, falling back to nobody at
/usr/sbin/spamd line 1147, <GEN193> line 4. 
Mar  4 16:39:09 hostname spamd[5227]: spamd: checking message <[EMAIL 
PROTECTED]> for test:65534 
Mar  4 16:39:09 hostname spamd[5227]: mkdir /home/xxx/.spamassassin: Permission
denied at /usr/share/perl5/Mail/SpamAssassin.pm line 1530 
Mar  4 16:39:09 hostname spamd[5227]: mkdir /home/xxx/.spamassassin: Permission
denied at /usr/share/perl5/Mail/SpamAssassin.pm line 1530 
Mar  4 16:39:09 hostname spamd[5227]: locker: safe_lock: cannot create tmp
lockfile /home/xxx/.spamassassin/auto-whitelist.lock.hostname.org.5227 for
/home/xxx/.spamassassin/auto-whitelist.lock: Permission denied 
Mar  4 16:39:09 hostname spamd[5227]: auto-whitelist: open of auto-whitelist
file failed: locker: safe_lock: cannot create tmp lockfile
/home/xxx/.spamassassin/auto-whitelist.lock.hostname.org.5227 for
/home/xxx/.spamassassin/auto-whitelist
.lock: Permission denied 
Mar  4 16:39:09 hostname spamd[5227]: spamd: identified spam (12.9/5.0) for
test:65534 in 0.6 seconds, 2876 bytes. 
Mar  4 16:39:09 hostname spamd[5227]: spamd: result: ...

This is consistent in that it will always be looking in
$PREVIOUS_VALID_USER/.spamassassin rather than $NOBODYS_HOME/.spamassassin.

I have had a poke around in the code and it looks something like
signal_user_changed should be called from handle_setuid_to_user but I am not
certain of the correct resolution.  I don't think this will cause any security
issues unless somebody has set their db files to be o+rw (which would be a hole
in itself).



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to