<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Perhaps someone else has an answer for this.<br>
Nothing in coderman's short answers have made this clear to me. The
answers look rather confusing to me, sorry.<br>
How could someone remotely access port 9051 on my computer protected by
a physical firewall, when the firewall is blocking access to that port?<br>
<br>
Someone else that knows more about this, please answer and explain.<br>
What are the risks running a version pre 0.1.2.16 or pre .0.2.0.4alpha
if a server/client is protected by a physical firewall?<br>
<br>
Thanks,<br>
Viking<br>
<br>
<br>
<br>
coderman skrev:
<blockquote
cite="mid:4ef5fec60708040548u28846a3agc155044a90486d6c@mail.gmail.com"
type="cite">
<pre wrap="">On 8/4/07, <a class="moz-txt-link-abbreviated" href="mailto:vikingserver@gmail.com">vikingserver@gmail.com</a> <a class="moz-txt-link-rfc2396E" href="mailto:vikingserver@gmail.com"><vikingserver@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> So in order to get attacked and get the torrc file modified, you first have
to get infected by a worm, virus, malware or trojan horse that communicates
with localhost:9051?
</pre>
</blockquote>
<pre wrap=""><!---->
no.
</pre>
<blockquote type="cite">
<pre wrap=""> There is no way that someone could directly attack me through port 9051
behind a physical firewall? Is this correct?
</pre>
</blockquote>
<pre wrap=""><!---->
what do you mean directly? your firewall protects against remote
connections, but direct connections can be made from localhost.
</pre>
<blockquote type="cite">
<pre wrap=""> If this is correct, then the chance of getting attacked behind a physical
firewall is very low, right?
</pre>
</blockquote>
<pre wrap=""><!---->
no.
best regards,
</pre>
</blockquote>
</body>
</html>