Hi, Baris Simsek <[EMAIL PROTECTED]> writes:
> I've just noticed that, you are using clamav user (Thanks to afsin). As probably most of us? Or I'm wrong? ;-) > After -r4 qsheff creates the spool directory with limited permissions > for local privacy reasons. So clamd need to run under 'root' user to > scan this directories. > > Please change clamav user to root and try again. You're right - now it works! But... maybe... setting the spool directory to another umask/owner also fixes the thing? I don't know how safe the clamd's local cocket really is, how about buffer overflows, and such things? The question remains - what is more unsecure: running clamd as root or having an insecure spool? > Note: Since clamd uses local socket, it is not insecure. Don't worry > about it. I have another idea will solve both local privacy problem and > secure running of clamd. It may come with the next revision. OK. I'll run clamd as root as a temporary solution, and I'm waiting for the next release of qsheff. :-) Thanks, -Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
