[erlang-questions] Disable Distribution

[Magnus Henoch]

Yes, leaving out the -sname/-name option is enough. You can verify this by
looking for open ports for "beam" processes with netstat:

$ netstat -ltpn | grep beam

With -sname, it shows one open port:

tcp        0      0 0.0.0.0:36551           0.0.0.0:*
LISTEN      29262/beam.smp

Without -sname, it shows nothing.

Regards,
Magnus



On Thu, Apr 14, 2016 at 5:29 PM, Feiko Nanninga <fnanninga@REDACTED>
wrote:

> As it turns out, I can leave -sname/-name and -setcookie out in vm.args
> as long as I do not use relx's extended starting script.
>
> But will that be enough to keep other nodes from connecting?
>
>
> On 14.04.2016 18:00, Feiko Nanninga wrote:
> > Hello,
> >
> > I'd like to deploy a non-distributed application with a sane
> > security configuration (preferably using a relx release).
> >
> > How can I entirely disable other nodes from connecting? Is there an
> > option to pass to erl (to add in vm.args)?. It seems using a release
> > requires me give the node a name and set a cookie. Now I can hope nobody
> > guesses the cookie or I can keep other users on the same system from
> > reading files which contain the cookie; but this is not a clean solution.
> >
> > Would not setting -sname or -name achieve this goal?
> >
> > Best regards,
> > Feiko
> >
> >
> > PS: If you don't provide vm.args yourself, relx generates one for you
> > with a predictable cookie. This is a BAD default.
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://erlang.org/mailman/listinfo/erlang-questions
> >
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160414/ef664e1c/attachment.htm>