Is there a Good Way to force ownership (both user and group) on a milter socket? I see that smfi_opensocket() honors umask, but that doesn't help with the GID, and dkim-filter doesn't seem to be picking up the primary GID of its -u argument:
$ id -a dkim-filter uid=128(dkim-filter) gid=128(dkim-filter) groups=128(dkim-filter) $ ls -l /var/run/dkim-filter/dkim-filter.sock srwxr-xr-x 1 dkim-filter root 0 2007-06-15 11:44 /var/run/dkim-filter/dkim-filter.sock Why this matters: Postfix apparently (quite reasonably) will happily drop all root privs after bind()ing to port 25 and before opening its connection to its milters; at least one Debian user reports being unable to connect to dkim-filter via UNIX socket as a result. Before I use a setgid bit or a chgrp in the init script, I was curious if there's a supported way to do this in libmilter (or if this is just an oversight in dkim-filter, for that matter). Thanks, -- Mike Markley <[EMAIL PROTECTED]> There is an order of things in this universe. - Apollo, "Who Mourns for Adonais?" stardate 3468.1 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
