<div>Ok - I may not be able to lock in the SSH to a particular IP, but can ofcourse try port-knocker and a non-password-based SSH. I will research a bit about these as i'm not very familiar with a port-knocker and a non-password-based SSH yet.<br>
<br>Thanks for your advice again. Thanks to Keith too. :o)<br><br> </div>
<div><span class="gmail_quote">On 2/12/08, <b class="gmail_sendername"><a href="mailto:A.L.M.Buxey@lboro.ac.uk">A.L.M.Buxey@lboro.ac.uk</a></b> <<a href="mailto:A.L.M.Buxey@lboro.ac.uk">A.L.M.Buxey@lboro.ac.uk</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>> have pasted and also the advice on keeping the SSH on a different port.<br><br>run SSH on a different port? oka, dumb scanners wont find it, but<br>
others will. just dont use password-based SSH and dont let it be wide<br>open to the whole internet (firewall it to the addresses you need - and<br>add in a port-knocker if you do need to open from a different location)<br>
<br>alan<br></blockquote></div><br>