3 ms·
Are you suggesting to bind to localhost in addition to a firewall, or are you anti-firewall? The firewall solution to a new/unexpected open port is a default d
by 8organicbits 4y ago
Are you suggesting to bind to localhost in addition to a firewall, or are you anti-firewall?
The firewall solution to a new/unexpected open port is a default deny rule. That's a commonly used best practice. There's nothing to forget.
- codedokode 4y ago> The firewall solution to a new/unexpected open port is a default deny rule. In case with a single node, it doesn't make sense. If you open a port, you probably want to be able to connect to it, otherwise why would you open it? And if you don't want anyone to connect, then don't open a port. There is no need for a firewall in case with a single node, unless you want custom rules like "only host A can connect to host B". There should not be "unexpected" open ports. Software should not open ports on external interfaces unless permitted by administrator. RabbitMQ should just have a switch to disable all unnecessary clustering features, but for some reason they don't want to implement it.