[prev in list] [next in list] [prev in thread] [next in thread]
List: qmail-scanner-general
Subject: [Qmail-scanner-general]Problems with ownership of qmail-scanner-queue.pl
From: Luca Maltese <luca.maltese () tnnconsulting ! com>
Date: 2005-03-05 23:14:10
Message-ID: ccecffa79cb37d58c4c8ed4a2f246467 () 81 ! 208 ! 68 ! 203
[Download RAW message or body]
Hi all
I found in this forum many people that told about my problem. So I
try to fix it as in the reply post but without success.
I Installed Q-S 1.25 in my mandrake 10.1 with perl 5.8.5. I compiled
maildrop-1.8.0 with the --enable-maildrop-uid=qscand option and
everything went ok.
when i compile Q-S 1.25 all went ok. but when I run
./contrib/test_installation.sh i recive a 430qq error
and in qmail-queue.log i find this error
Sat, 05 Mar 2005 21:53:01 CET:12590: error_condition:
X-Qmail-Scanner-1.25: owner of unpacked file
"/var/spool/qmailscan/tmp/rayfw.rayberndston.it111005598149312590/11100559
81.12592-0.rayfw.rayberndston.it" (uid=0) doesn't match UID of
Qmail-Scanner (uid=500) - can't expect this to work. Fix whatever is
creating files with uid=0
First of all I checked the permission in /var/spool/qmailscan/ and
it is qscand:qscand as in subdirs (to be sure I forced with chown -R
qscand:qscand without success)
in second stage I modify the clamd user in Clamd.conf file using
qscand.
Now clamd and spamassassin works. Q-S 1.25 works only if I change
the ownership in root:root (and not qscand:qscnad) and i run
clamdscan as root (modifing clamd.conf file)
How can I fix this perms problem? I can't use Q-S 1.25 as root, I
think it is a security hole, isn't it? please help me.
Luca
[Attachment #3 (text/html)]
<html><head><meta http-equiv=Content-Type \
content="text/html;charset=ISO-8859-1"><meta content="Group-Office 2.11" \
name="GENERATOR"></head><body><p>Hi all</p><p>I found in this forum many people that \
told about my problem. So I try to fix it as in the reply post but without \
success.</p><p>I Installed Q-S 1.25 in my mandrake 10.1 with perl 5.8.5. I compiled \
maildrop-1.8.0 with the --enable-maildrop-uid=qscand option and everything went \
ok.</p><p>when i compile Q-S 1.25 all went ok. but when I run \
./contrib/test_installation.sh i recive a 430qq error</p><p>and in qmail-queue.log i \
find this error</p><p><font><em>Sat, 05 Mar 2005 21:53:01 CET:12590: error_condition: \
X-Qmail-Scanner-1.25: owner of unpacked file \
"/var/spool/qmailscan/tmp/rayfw.rayberndston.it111005598149312590/11100559<br \
/>81.12592-0.rayfw.rayberndston.it" (uid=0) doesn't match UID of Qmail-Scanner \
(uid=500) - can't expect this to work. Fix whatever is creating files with \
uid=0</em></font></p><p>First o f all I checked the permission in \
/var/spool/qmailscan/ and it is qscand:qscand as in subdirs (to be sure I forced with \
chown -R qscand:qscand without success)</p><p>in second stage I modify the clamd user \
in Clamd.conf file using qscand.</p><p>Now clamd and spamassassin works. Q-S 1.25 \
works only if I change the ownership in root:root (and not qscand:qscnad) and i run \
clamdscan as root (modifing clamd.conf file)</p><p>How can I fix this perms problem? \
I can't use Q-S 1.25 as root, I think it is a security hole, isn't it? please help \
me.</p><p>Luca</p><p /><p /></body></html>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Qmail-scanner-general mailing list
Qmail-scanner-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic