You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
doc: correct the <user>/<group> privilege-dropping documentation
The manual claimed the server drops privileges when launched as root. It no
longer does: <user>/<group> are deprecated and ignored. Document this, advise
against running as root, and list the supported ways to serve ports 80/443 as
an unprivileged user. Remove the misleading <user>/<group> lines from the
sample configurations.
{3 [<user>] and [<group>] : user who runs the server}
334
328
335
329
336
-
If the server is launched by root, it will change itself the user and group for the process, for security reasons. Create a group and a user for Ocsigenserver or use an existing user of your system (e.g. [www-data]).
337
-
338
-
Example :
330
+
{b Deprecated and ignored.} Ocsigenserver no longer drops privileges: these
331
+
tags are accepted for backward compatibility but have {b no effect}, and the
332
+
server logs a warning if they are present.
339
333
334
+
{b Do not launch the server as root.} Run it directly as a dedicated
335
+
unprivileged user (e.g. [www-data]). To serve a privileged port (80 or 443)
336
+
as a non-root user, use one of:
337
+
- a reverse proxy (nginx, HAProxy, Caddy, ...) terminating ports 80/443 and
338
+
forwarding to Ocsigenserver on a high port (recommended, see the [<timeout>]
339
+
note above);
340
+
- the Linux capability [cap_net_bind_service] on the executable
341
+
([setcap 'cap_net_bind_service=+ep' ...]);
342
+
- a firewall/port redirection from 80/443 to a high port.
0 commit comments