1. User may not expect that the package contains some services. epmd.socket is internal erlang thing.
2. epmd.socket is listening on 127.0.0.1 by default. Though currently it leads to constant complaining, this was required by security team at the time when epmd.socket was introduced. It is minimal working local configuration and it should be fine until you really need distribution setup.
3. erlang has its own default hard-coded way to start epmd. It just execs new epmd process every time when it cannot connect to existing one. So, while epmd.socket is not active, any erl command invocation leads to starting new epmd process that listens on 0.0.0.0. Is it more secure?
I agree with Matwey. It is enough to execute and erlang command and the epmd will listen to 0.0.0.0 I think that that this is a bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1124947 (I opened it) It is not clear the beahaviour for the final user. We had to implement a few workarounds to handle the situation described to https://bugzilla.opensuse.org/show_bug.cgi?id=1124947#c0 We'd like to find a solution instead avoiding workarounds. Thank you -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org