From: "curby ." <curby.public@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: SSH Brute force attacks - Script version 1.0
Date: Mon, 27 Jun 2005 00:24:58 -0600 [thread overview]
Message-ID: <5d2f379105062623243240e265@mail.gmail.com> (raw)
In-Reply-To: <002e01c579e1$4d326d00$4206a8c0@loki>
On 6/25/05, Marius Mertens <marius.mertens@gmx.de> wrote:
> > (3) Also, is this the only position for the negation that makes the
> > rule work as intended?
>
> Yes, you are telling the recent module to do an rcheck in the list,
> the --seconds and --hitcount just specifiy further criteria for that rcheck.
> The negation belongs to the whole rcheck construct, you cannot invert just
> single comparisons within that. Btw, be careful there, at least with my
> installation an incorrectly placed "!" does not trigger an error message,
> but is just ignored, so your rule might do the opposite of what you wanted
> it to do. For details and where negations are valid you can also have a look
> at "iptables -m recent --help"
Ah, indeed that command shows that --seconds and --hitcount cannot
take a negation. I was going by
http://www.netfilter.org/documentation/HOWTO//netfilter-extensions-HOWTO-3.html#ss3.16
which shows that almost all options can take a negation. Reading the
fine manual was my downfall. =)
Thank you for the informative response.
next prev parent reply other threads:[~2005-06-27 6:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 18:58 SSH Brute force attacks - Script version 1.0 curby .
2005-06-25 23:54 ` Marius Mertens
2005-06-26 20:46 ` Jan Engelhardt
2005-06-27 8:18 ` Marius Mertens
2005-06-27 15:53 ` curby .
2005-06-27 16:09 ` Stephen Frost
2005-06-27 6:24 ` curby . [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-06 15:57 SSH Brute force attacks Brent Clark
2005-06-02 18:26 ` SSH Brute force attacks - Script version 1.0 Taylor, Grant
2005-07-25 19:41 ` Steven M Campbell
2005-07-26 6:18 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d2f379105062623243240e265@mail.gmail.com \
--to=curby.public@gmail.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox