<html>
<body>
<font size=3>At 04:42 PM 2/10/2010, Jay Foster wrote:<br>
<blockquote type=cite class=cite cite="">On 2/10/2010 12:48 PM,
mythtv-users-request@mythtv.org wrote:<br>
<blockquote type=cite class=cite cite="">In
article<3d82ce5f1002091220k6154d53alcd4ee1b1ca1f257a@mail.gmail.com>,<br>
Kenneth Emerson wrote:<br>
<blockquote type=cite class=cite cite="">> Once you open up port
22 on your mythtv box to the internet, it will be hit<br>
> by computers trying to hack into it (check out logwatch to
find out).</blockquote>I use my broadband router to map a different port,
only have one user allowed<br>
to SSH in, and the password is 12+ characters with a mix of cases,
numeric<br>
and punctuation. No problems yet!<br><br>
Ian<br>
</blockquote><br>
I have done the same thing. However, I noticed that the netbots
would find my machine on port 22 and start banging away on it. They
never succeeded in gaining access, but I didn't like all the extra
activity on my machine. This extra activity would also look to my
ISP provider as either SPAM or me running a server, so my ISP would reset
my DSL resulting in a new public IP address. This was annoying and
made accessing the Myth system from outside more difficult when my public
IP address would keep changing frequently.<br><br>
To stop that, I also turned on the firewall on my Myth system to only
allow access from the local networks and 1 public network (my work
network). This stopped the netbots in their tracks. I could
have done the same with my firewall/router, but it doesn't have that
functionality (only does port forwarding/blocking).<br><br>
Jay</font></blockquote><br>
I use Dynamic DNS from a free supplier
(<a href="http://www.no-ip.com/" eudora="autourl">http://www.no-ip.com</a>
) to keep my server accessible regardless of ISP public IP address
changes. You just run a small client on the server and it guarantees that
the domain will always resolve back home. <br><br>
-- Mache</body>
</html>