From: "curby ." <curby.public@gmail.com>
To: Netfilter User Mailing List <netfilter@lists.netfilter.org>
Subject: SSH Brute Force not working (any longer)
Date: Wed, 27 Jul 2005 10:36:57 -0600 [thread overview]
Message-ID: <5d2f37910507270936737ad3d1@mail.gmail.com> (raw)
I know enough to realize that it didn't stop working just because it
hates me: most likely, i changed something in the configuration or
something to make it stop working. However, I can't think of anyting
I could have done to two different machines to make them stop working
in exactly that same way. Basically, every SSH attempt skips the
return to the input chain and jumps directly to log/drop or
log/tarpit. I've tried increasing the --hitcount, tried rebooting or
otherwise restarting the network service, tried using a different
--name in recet, etc.
I have tried all the following scripts (I can paste their contents in
if requested but it would be rather annoying because of their combined
length) with no success. Any ideas on what might have happened?
Kernel version and iptables version didn't change, the recent module
loads with no errors, and all the iptables commands to insert rules
complete with no errors.
Links to variations that I tried with no success:
http://curby.net/doc/testwall1
http://curby.net/doc/testwall2
http://curby.net/doc/testwall3
http://curby.net/doc/testwall4
Hopefully it's a really simple typo or something, though with all the
variations I've tried, I'm starting to doubt that simple explanation.
What might the problem be? Thanks!
next reply other threads:[~2005-07-27 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 16:36 curby . [this message]
2005-07-27 18:31 ` SSH Brute Force not working (any longer) Nagy Zoltan
2005-07-27 19:14 ` Marius Mertens
2005-07-27 21:55 ` Marius Mertens
2005-07-27 22:50 ` curby .
2005-07-27 23:33 ` Marius Mertens
2005-07-28 19:28 ` Taylor, Grant
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=5d2f37910507270936737ad3d1@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