From: "Lpct" <lpct@linux.pctools.cl>
To: netfilter@lists.netfilter.org
Subject: Re: SSHBrute Force: False Postives
Date: Thu, 1 Feb 2007 1:28:31 -0000 [thread overview]
Message-ID: <20070201042831.DD4F532A702@linux.pctools.cl> (raw)
--------- Mensagem Original --------
De: Dominic Caputo <jec6jec6@gmail.com>
Para: netfilter@lists.netfilter.org <netfilter@lists.netfilter.org>
Asunto: SSHBrute Force: False Postives
Fecha: 01/02/07 02:30
>
> I have been reading up on iptables and i am by no means an expert but i
have
> a problem with SSH brute force attacks on port 22. I am currently using
the
> config below to minimise these threats but i am constantly getting false
> positives (logs actually say that my connection has been flagged as a
brute
> force connection even on the on the first attempt-but then on others it
> connects first time with no problems)
>
> #SSH Brute-Force Scan Check
> $IPTABLES -N SSH_Brute_Force
> $IPTABLES -A INPUT -p tcp --dport 22 -m state --state NEW -m recent --name
> SSH --set --rsource -j SSH_Brute_Force
> $IPTABLES -A SSH_Brute_Force -m recent ! --rcheck --seconds 60 --hitcount
> 4 --name SSH --rsource -j ACCEPT
> $IPTABLES -A SSH_Brute_Force -j LOG --log-level info --log-prefix
"SSH Brute
> Force Attempt: "
> $IPTABLES -A SSH_Brute_Force -p tcp -j DROP
>
> Any help with this problem would be great
>
> Dominic
>
.... you can start changing the ssh port from 22 to xxx... this doesnt solve
your problem, but this mesure minimize this kind of attack like a 70%
________________________________________________
linux.pctools.cl
next reply other threads:[~2007-02-01 1:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 1:28 Lpct [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-01 2:28 SSHBrute Force: False Postives Dominic Caputo
2007-02-01 12:06 ` Wakko Warner
[not found] ` <20070201131319.71585.qmail@web25512.mail.ukl.yahoo.com>
2007-02-01 23:17 ` Wakko Warner
2007-02-02 14:38 ` Michael Rash
2007-02-02 17:26 ` Wakko Warner
2007-02-02 20:39 ` franck
2007-02-01 16:32 ` fender
2007-02-01 21:30 ` Brad Lhotsky
2007-02-06 20:53 ` R. DuFresne
2007-02-06 21:12 ` franck
2007-02-07 2:01 ` Michael Rash
2007-02-08 3:17 ` fender
2007-02-09 0:17 ` Michael Rash
2007-02-12 13:10 ` fender
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=20070201042831.DD4F532A702@linux.pctools.cl \
--to=lpct@linux.pctools.cl \
--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