Re: daemontools control over sophie not working any more since release 3.04

[email protected] Mon, 26 Sep 2005 10:46:59 +0900
Newsgroups gmane.comp.security.virus.vtools
Message-ID <OF21C42890.4413F88C-ON49257088.0009927F-49257088.0009C92F@sophos.com>
Uwe,

Sophie 3.04 and Sophie 3.04rc1/2 both switch to an unprivledged user (the
one specified in the user:, group: options in the sophie config file)  to
perform scans.  The difference is where they actually switch to this user.

Lets assume sophie is started as root.  In 3.04rc2, the main process will
be running as root, which forks child processes to perform the actual
scans.  The first thing these child processes to is a setgid, setuid to the
non-root user, group (or whatever is specified in sophie.cfg).  In 3.04,
the main process performs the setgid, setuid before the main loop so the
main process and child processes are all running as the non-root user.
This change was necessary because of some semaphores that were added to
libsavi.  These have since been removed temporarily I believe, so 3.04rc2
should work again.

However, since both versions switch to an unprivileged user, and they use
the same code to do so, I'm not sure why you are having problems now.  If
you could provide some more detail as to what exactly the problem is, the
Sophie log, etc, then maybe we can help you out.

Scott.

[email protected] wrote on 09/20/2005 06:18:50 PM:

> Hello List,
>
> we are using sophie 3.04rc1/2 under the daemontools control for years
> without any problems.
> Since the last update to release 3.04 there seems to be a significant
> change in the way how sophie handles subprocesses.
> I read that sophie is now responsable for starting subprocesses which
> are run under an unprivileged user account. Does that mean that sophie
> now needs to be run as root to be able to change the user for the
> subprocess?
> We never ran sophie as root so far. Under daemontools we always changed
> to an unprivileged user with the setuidgid command before starting
sophie.
> Is version 3.04 not compatible with daemontools any more? If so, was the
> change in source code absolutely necessary to work properly? What to do
> to make it work under daemontools?
>
> Thanke You, Uwe
> _______________________________________________
> vtools mailing list
> [email protected]
> http://www.vanja.com/list/listinfo.cgi/vtools