Thanks Olivier, I have use this metod and this resolve the Q-S problem, but clamd not work propertly.
Then it is a problem with clamd, not Q-S anymore ;-)
What is wrong with clamd exactly when you make it run as qscand? It's working
fine on my systems.
I have do this command for resolve the problem: a) process pid file b) log rotations
------- usermod -G clamav qscand chmod g+w /var/run/clamav perl -p -i -e 's/create 640/create 660/' /etc/logrotate.d/clamd -------------
Is this a potential security issue?
Sorry I am not sure I understand what you mean. You put qscand in the group clamav,
and then gave group-write permission on the clamav run directory and log files?
Why not simply chown the files to qscand? Basically you do not use the user "clamav" anymore,
and replace it with qscand everywhere.
i.e: 'chown -R qscand /var/run/clamav' etc..
But anyway what you did should not be a security issue, since both the qscand and
clamav group/user are normally restricted to their relevant process, and the other
way around. Thus I guess it would be secure as long as those processes and users are
secure, which is completely other issue ;-)
Olivier
------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
