From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Taylor, Grant" Subject: Re: SSH Brute force attacks Date: Sat, 21 May 2005 17:37:19 -0500 Message-ID: <428FB81F.6030403@riverviewtech.net> References: <427B93EE.3030905@eccotours.dyndns.org> <42898402.10507@eccotours.dyndns.org> <4289E72F.7020901@wp.pl> <200505211200.28314.pvolkov@mics.msu.su> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200505211200.28314.pvolkov@mics.msu.su> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii"; format="flowed" To: netfilter@lists.netfilter.org > Why this update here (see below)? > > $ipt -A SSH_Brute_Force -m recent --name SSH --update > > Every time packet passed --set rule it updates SSH. So if drop this rule, > nothing changes. Or am I wrong? Is there any idea behind this that I missed. The "--set" rule is required because the testing that I did the "--update" rule would not effectively do the same thing as "--set" because there was no initial "--set" to be updated. It's sort of a chicken and egg problem where you can not successfully have one with out having the other in this scenario. The only draw back to having the "--set" that I'm aware of is that the hit count is incremented once per "--set" and "--update" thus you have to double the "--hitcount" value that you want to match against. Grant. . . .