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".
pgpSkJTPBCAjA.pgp
Description: PGP signature
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
