hi
> > I started debugging and found that /var/qmail/queue/lock/trigger was:
> > prw------- 1 qmails qmail 0 Mar 2 15:36 trigger
> [...]
> > I set ownership and permissioins to:
> >
> > prw-r----- 1 qmailq qmail 0 Mar 2 15:51 trigger
> >
> > is this a known bug ? Any security problems with my modifications ?
> > (i dont see any....)
>
> Leave the ownership of the trigger alone, and change the permissions to
> rw--w--w- .
hu ? You mean allowing any local user to cat /dev/zero >trigger
is the better idea ? Giving non-trusted processes write access
to a pipe of a daemon (running with root-privilieges) is never
a good idea tought.
Which qmail daemon/process also needs to write to the trigger ?
It works fine here with qmailq.qmail/640...(or at least qmail seems to
work as expected :>)
skyper
--
PGP: dig @segfault.net skyper axfr|grep TX|cut -f2 -d\"|sort|cut -f2 -d\;
