<div>Another note is to run ssh on another port other than 22, i.e. 9922, and configure ssh to disconnect the connection after 3 attempts.</div>
<div> </div>
<div>Dave<br><br> </div>
<div><span class="gmail_quote">On 6/27/06, <b class="gmail_sendername">Laurence Southon</b> <<a href="mailto:laurence@southon.uk.net">laurence@southon.uk.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Ritchie Fraser wrote:<br>><br>> Is it just a case of poking a hole in my dad's router's firewall and also
<br>> forwarding ssh traffic to his PC?<br>><br><br>Do be careful with this. I've had a server compromised despite disabling<br>root logins and using strong passwords.<br><br>You would do well to allow ssh logins with keys only.
<br><br>Regards,<br><br>Laurence Southon<br><br>_______________________________________________<br>Kent mailing list<br><a href="mailto:Kent@mailman.lug.org.uk">Kent@mailman.lug.org.uk</a><br><a href="https://mailman.lug.org.uk/mailman/listinfo/kent">
https://mailman.lug.org.uk/mailman/listinfo/kent</a><br></blockquote></div><br>