<br><br><div><span class="gmail_quote">On 1/26/06, <b class="gmail_sendername">John Summerfied</b> <<a href="mailto:debian@herakles.homelinux.org">debian@herakles.homelinux.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Steven J Lamb wrote:<br>> I am trying to create a script to block people using hosts.deny. I<br>> realize that I should just block everyone and then open access for those<br>> whom I know I trust but because of the nature of our network this is not
<br>> possible. basically I check log files for login attempts every five<br>> minutes and block those that attempt to log in more than 3 times that<br>> day.<br><br>This is too late. An automated attack may well be completed in this
<br>window of time.<br><br>Instead, use another port as a door-knock: when someone tries to connect<br>to <some port>, then allow connexions to ssh for a short time.<br><br>
</blockquote></div>Are there any benifits of doing this as opposed to changing the port used for ssh?<br clear="all"><br>-- <br>As a boy I jumped through Windows, as a man I play with Penguins.