3 ms·
I'm in the opposite camp, not because I think that you should be forced to do the privileged ports dance, but because I think you should bind to higher ports an
by GauntletWizard 4y ago
I'm in the opposite camp, not because I think that you should be forced to do the privileged ports dance, but because I think you should bind to higher ports and it should be your load balancer's work to do the translation. Everyone is running some form of load balancer, whether it be a NAT box, Nginx, Kube-proxy, etc.
The low-numbered internet ports are useful to avoid binding so that your machine that's only a shell host isn't used as an exploit server when a single user on it is compromised. It's useful to provide a minor barrier to understanding how a server works and port allocations are made before someone deploys their cool WebApp on a random ec2 machine.
Probably good advice if you're maintaining a base image for a k8s cluster or on the load balancer box itself or whatever to simply set the minimum port to 1, though.
- fomine3 4y agoWhat prevents port 3000 isn't used for exploit server? I argue opposite. Possibly newbie would run `sudo node` to run webapp on port 80, that is nightmare.
- GauntletWizard 4y agoNothing prevents that. Your average newbie is more likely to notice the port in the URL, though, that it's not an "Official" bank link or whatever. If you've got root, you will misconfigure no matter what you do. I'm not arguing against a root user - I'm arguing about machines you don't administer.
- worthless-trash 4y agoSo tcpmux has to run as root, why you hating on that ?