Andrew writes:
Can anyone tell me what the permissions are when you install
courier-authlib straight from it's tarball or from an rpm? I run
courier-authlib on FreeBSD and I've installed it from the FreeBSD port.
In that scenario the socket is created with permissions set to 777 and
is owned by root:courier but the directory it's in has permissions 750
and is owned by courier:courier.
This is correct. The default configuration allows for a site-specified
selection of the userid who will own everything. Creating a new "courier"
userid is a valid option, but so is recycling some suitable stock system
userid, such as "daemon". Ditto for the groupid. Notwithstanding the
selected userid/groupid, the authdaemon socket has mode 777, while the
ownership of the socket directory is set to the selected owner
userid/groupid, and mode 750.
If prior to building the rpm you create a "courier" userid and groupid, that
userid/groupid will take ownership of the authdaemon directory, and the
other files, otherwise it's going to be "daemon".
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier auth appl...
