-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run as user=nobody group=nogroup (OpenBSD) #162
Comments
Running the milter in foreground shows the problem.
By comparison, the log was silent when running as daemon. |
This is the server hello in May.
By comparison, the new version of the milter, using the same configuration, is trying to change directory, and it fails.
|
This is what happens when changing ownership.
However, I cannot run this as root:wheel with chroot on /. |
Are you able to run the server with user:group other than root? |
I would not recommend running as root, and instead using the options in the config file to drop privileges and run as an unprivileged user For example:
The chroot functionality is quite complicated, and the chroot build isn't simple unfortunately. Removing chroot from the config should be enough to disable this. |
I removed the chroot line fom the configuration, and set runas:rungroup as nobody:nogroup. This is what I see:
|
It is happy with nogroup, but demands root as user:
|
This warning needs to be more explicit:
|
The username and group are stated in the /etc file, and the pid file has ugo+w permissions anyway, so the problem is elsewhere.
The server shuts down without leaving an error log.
The server must chroot on "/" or it will fail; this is a security risk.
The previous version of the milter worked without interruptions since May.
This is an update, leaving the old configuration in place.
The text was updated successfully, but these errors were encountered: