Restricting distributed Erlang to one host
Sat Nov 22 13:21:20 CET 2003
You can use net_kernel:allow(Nodes) to make sure
that only the right nodes connect.
The nodes could make themselves known e.g.
through a http-based login procedure, or you
could easily write a gen_tcp-based registration
Hacking net_kernel.erl is perhaps a more manly
way to go about it, but hardly recommended.
In this case, the function to attack is setup/4,
an it would be a trivial hack.
On Sat, 22 Nov 2003 08:43:19 +0100, Carsten Schultz
> On Fri, Nov 21, 2003 at 07:48:20PM -0600, Martin J. Logan wrote:
>> Yeah, have your .erlang.cookie file be unique per host.
> Oh, I'm sorry, I was not clear enough in my original question. For
> security reasons I do not want to rely on cookies for this but want to
> have connections from different hosts being rejected right away.
More information about the erlang-questions