4 ms·
> The workaround > > On modern Linux systems, you can configure privileged ports using sysctl: Or you could just run your service on a non-privileged port - y
by Karellen 4y ago
> The workaround
>
> On modern Linux systems, you can configure privileged ports using sysctl:
Or you could just run your service on a non-privileged port - you don't have to stick to 80/443.
(If you really must have access to the service on the standard ports, you could set up an iptables/firewall rule to forward packets headed to port 80/443 to whatever port you're actually running your service on.)
- Skunkleton 4y agoIMO using socket activation via systemd is a reasonable approach. I don't see any reason a non-service account should be running a service on port 80.