Skip to content
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

Change unix sockets user to haproxy #504

Merged
merged 1 commit into from
Jan 19, 2020
Merged

Change unix sockets user to haproxy #504

merged 1 commit into from
Jan 19, 2020

Conversation

jcmoraisjr
Copy link
Owner

The internal ACME server (answer ACME challenges) and the http frontend (only if internal fronting TCP proxy is needed) uses unix sockets to the haproxy process communicate with. If the controller starts as root but use-haproxy-user is declared, haproxy wouldn't have permission to write to the socket. Now all sockets has haproxy as owner and 0600 as its permission, even if the process continue to run as root.

The internal ACME server (answer ACME challenges) and the http frontend (only if internal fronting TCP proxy is needed) uses unix sockets to the haproxy process communicate with. If the controller starts as root but `use-haproxy-user` is declared, haproxy wouldn't have permission to write to the socket. Now all sockets has `haproxy` as owner and `0600` as its permission, even if the process continue to run as root.
@jcmoraisjr jcmoraisjr merged commit d2dde01 into master Jan 19, 2020
@jcmoraisjr jcmoraisjr deleted the jm-socket-owner branch January 19, 2020 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant