<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span><br></span></div><div><span>Deny host, looks </span>cool!!</div><div><br></div><div>the other option would be to white list the IPs/subnets you will be accessing from, and deny the rest using firewall rules.</div><div><br></div><div>thanks</div><div>matti</div><div><br></div><div><br></div><div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "><font size="2" face="Arial"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Robert Leyva <mrflash818@geophile.net><br><b><span style="font-weight: bold;">To:</span></b> SGVLUG Discussion List. <sgvlug@sgvlug.net><br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, October 19, 2011 9:29 AM<br><b><span
style="font-weight: bold;">Subject:</span></b> [SGVLUG] ssh protection - advice desired - thanks<br></font><br>
Thanks for all the good advice.<br><br>robert@pip:~$ sudo aptitude install denyhosts<br>...<br>done!<br><br>...I'll see how denyhosts does for now, and keep tail-ing my auth.log<br><br><br>http://packages.debian.org/squeeze/denyhosts<br>http://denyhosts.sourceforge.net/index.html<br><br>-- <br>"Knowledge is Power" -- Sir Francis Bacon<br><br>Robert Leyva<br><a ymailto="mailto:mrflash818@geophile.net" href="mailto:mrflash818@geophile.net">mrflash818@geophile.net</a><br><br><br><br><br></div></div></div></body></html>