<br><br><div class="gmail_quote">On Wed, Feb 17, 2010 at 7:22 AM, Mike Holden <span dir="ltr"><<a href="mailto:mythtv@mikeholden.org">mythtv@mikeholden.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Mike Perkins wrote:<br>
> ...or some other port, forwarded to 443 on your server. Like 80, 443 is too<br>
> juicy a target for the bots to aim at. My firewall gets dozens of hits per hour<br>
> on both ports.<br>
<br>
This gets tricky for connecting from work though. A lot of companies are getting<br>
very security-conscious and blocking almost everything apart from http, shttp and<br>
ftp from exiting their user network onto the intertubes. I know I am unable to use<br>
non-standard ports for https etc.<br></blockquote><div><br><br>You could also forward a standard port to a non-standard service. A pain for a public server, but for your own personal box, not an issue. And if the bad guys are attacking 443 expecting Apache, and you have OpenSSH there, for example, it will give you some security. Still, it does cause some issues for a connecting without any added software on the client machine. If you properly set up 443 and keep updated, your chances of getting hacked are quite low. <br>
</div></div>