From: "curby ." <curby.public@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: NEW "SSH Brute Force " ruleset (20050628.0)
Date: Sat, 2 Jul 2005 11:13:41 -0600 [thread overview]
Message-ID: <5d2f379105070210137e0af6ca@mail.gmail.com> (raw)
In-Reply-To: <004801c57e70$1fad3890$4206a8c0@loki>
On 7/1/05, Marius Mertens <marius.mertens@gmx.de> wrote:
> Add a host to a special whiltelist after doing something special, like
> connecting to a certain port, which would lower the risk of a DOS (they can
> still try, but you can override it)
I've been considering this too. It's actually a simple form of port
knocking that can be implemented exclusively in iptables (without the
need of extra tools). The primary goal of port knocking is to foil
port scans, but it could be applicable here.
To protect against DoS, is there any easy way of requiring that three
packets be transferred in an SSH connection before it triggers a
recent update? Since someone spoofing source IPs to DoS would be
unlikely to continue the connection with the server, such DoS attacks
might be foiled more effectively this way than using rttl (which the
attacker can just exhaustively try all values for).
next prev parent reply other threads:[~2005-07-02 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 7:10 NEW "SSH Brute Force " ruleset (20050628.0) Taylor, Grant
2005-07-01 19:07 ` Marius Mertens
2005-07-02 17:13 ` curby . [this message]
2005-09-03 22:08 ` Grant Taylor
2005-09-04 5:01 ` /dev/rob0
2005-09-04 19:59 ` /dev/rob0
2005-09-05 20:14 ` /dev/rob0
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=5d2f379105070210137e0af6ca@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