Should a more secure cluster be achieved by restricting listening IP? #8907
-
Is your feature request related to a problem? Please describe.Describe the solution you'd likeJust like the following configuration:
Describe alternatives you've consideredNo response Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
The address on which EPMD listens is already configurable: https://www.rabbitmq.com/networking.html#epmd-interface While restricting the interfaces on which EPMD is listening is reasonable, assigning non-standard ports to everything is just pointless and confusing security-by-obscurity if you ask me. But it's up to you. |
Beta Was this translation helpful? Give feedback.
-
One more thing that should be mentioned is that epmd communication protocol is very limited and some operations am an inly be performed by a client (such as a RabbitMQ node) that runs on the same host. So the attack surface is tiny, and all communication that happens after peer host and port discovery via epmd, still uses a shared secret authentication mechanism. |
Beta Was this translation helpful? Give feedback.
The address on which EPMD listens is already configurable: https://www.rabbitmq.com/networking.html#epmd-interface
While restricting the interfaces on which EPMD is listening is reasonable, assigning non-standard ports to everything is just pointless and confusing security-by-obscurity if you ask me. But it's up to you.