Sam Varshavchik wrote:
Bob Kinney writes:
I'm just trying to understand the security issues caused by either solution and the reasons behind the apparent change in behavior of the rpm install.
There are no changes. The configuration scripts checks which system accounts are present. If one called "courier" exists, this userid will own the Courier installation. If it doesn't exist, the script checks for "daemon", and several others, in order to determine the primary userid for installation.
If you build RPMs on one machine, and install the RPMs on a second machine, then the system accounts on both machines must be identical.
Why not let the courier packages create the user courier? (Or get really fancy create a package courier-user or courier-base, let all other packages depend on that. That way you can remove the courier user when this package is removed).
M4
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
