Timeline for Allow non-root process to bind to port 80 and 443?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 15, 2021 at 19:12 | history | suggested | Nathan Tuggy | CC BY-SA 4.0 |
Linkification, better formatting
|
| Jul 15, 2021 at 17:16 | review | Suggested edits | |||
| S Jul 15, 2021 at 19:12 | |||||
| Jan 22, 2021 at 7:27 | comment | added | Dale Hagglund | @jontejj I'm not familiar with it so I can't say. | |
| Jan 22, 2021 at 5:34 | comment | added | jontejj | auth-bind seem to be the way to go for one-offs? | |
| Jan 22, 2021 at 3:55 | comment | added | Dale Hagglund | @jontejj Just to make sure I'm clear, you're talking about a program that accepts a port number to listen on via the command line? I'd start by seeing if there was any way to use a non privileged port, to avoid needing root privs. There might be a way to use linux capability tools to assign just the right to open privilege ports when you run the program. | |
| Jan 21, 2021 at 21:34 | comment | added | jontejj | Probably good advice if you are designing the program. If you just want to run a program that accepts a port as an argument, what would you do then? | |
| Feb 2, 2014 at 9:59 | comment | added | Dale Hagglund | What your proposing isn't considered best practice. You might look at inetd, which can listen on a privileged socket and then hand that socket of to an unprivileged program. | |
| Feb 2, 2014 at 6:49 | history | answered | Dale Hagglund | CC BY-SA 3.0 |