3 ms·
Why do people use non-standard ports for public internet-facing services? To me it just smells of "we don't have enough public IP's, and still manage our netwo
by londons_explore 7y ago
Why do people use non-standard ports for public internet-facing services?
To me it just smells of "we don't have enough public IP's, and still manage our network with port-forwarding rather than a proper application level loadbalancer".
That matches my observations that 'ancilery'services frequently seem to be on non-standard ports - like the employee login portal, the company webchat service, the analytics service, etc.
- closeparen 7y agoOld school network engineers are more comfortable with firewall rules and routing tables than nginx configs?
- shanemhansen 7y agoTo me it smells of "we are running some random app server as a non-profit user and need to bind to a high numbered port"
- zozbot234 7y ago> we don't have enough public IP's I mean, we kinda knew that already. Port numbers give you a free 16-bit address space per public IP, that's nothing to sneeze at.
- Thriptic 7y agoSecurity through obscurity is one reason. A lot of script kiddies will blast away at services on well known ports. Simply changing the port off the default cuts down on a lot of script based attacks, inhibits generic port scans, and makes it easier to differentiate a deliberate, human attacker from a script. In this specific case, I don't know. Perhaps rotating through ephemeral ports is done to mess with simple traffic filtering rules on firewalls?