On Dec 3, 2007 1:30 PM, Michael Regen <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Dec 3, 2007 11:07 AM, Per Hedeland <<a href="mailto:firstname.lastname@example.org" target="_blank">email@example.com</a>> wrote:<br></div><div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Then again, everyone seems to think that the<br>Erlang distribution is inherently unsafe anyway (for reasons that aren't
<br>obvious to me at least)...<br><font color="#888888"><br>--Per Hedeland<br></font></blockquote></div></div><br>I can just talk about myself. And I simply do not know whether it is safe or not. I have not seen any reviews of it, neither bad nor good ones and I assume that its ability to withstand attacks is not tested much because I assume that most Erlang nodes are operated in a safe environment. Remember, even OpenSSH had it's troubles. One of the design goals of OpenSSH was to operate it in the wild. I do not know whether this was also one of the design goals of Erlang distribution. I tend to deny this since I read distribution_handshake.txt ("This is not entirelly safe, as it is vulnerable against takeover attacks, but it is a tradeoff between fair safety and performance.").
<br>Erlang SSL distribution is currently broken. You cannot control which IP address epmd binds to...<br><br>I think in the area of IT security you have to choose the defensive approach. You need a proof or very good hints that something is secure before you can assume it to be secure. Therefore I handle Erlang distribution as if it were unsafe.
<br><br>By the way I am only referring to open source Erlang. I cannot say anything about the commercial version of Erlang.<br><br>Cheers,<br><font color="#888888">Michael<br><br></font></blockquote><div>Maybe already a bit off topic, however: The most simple form of a denial of service attack consists of sending the bytes 0x00, 0x01, 0x6B to your epmd port causing epmd to shut down, rendering all nodes on this system unavailable for subsequent connection attempts of new distributed nodes. Established connections are not affected, I think.
<br><br>Heart does not help here. Also restarting epmd does not help except you find a way to re-register your running nodes to epmd (which is possible I guess).<br></div></div><br><br>Cheers,<br>Michael<br>