From: "Dmitry S. Makovey" <dmitry@athabascau.ca>
To: gentoo-user@lists.gentoo.org
Cc: Steve <Gentoo_sjh@shic.co.uk>
Subject: Re: [gentoo-user] Curious pattern in log files from ssh...
Date: Thu, 04 Dec 2008 08:50:27 -0700 [thread overview]
Message-ID: <200812040850.31069.dmitry@athabascau.ca> (raw)
In-Reply-To: <493726CA.8080207@shic.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
On December 3, 2008, Steve wrote:
> Dmitry S. Makovey wrote:
> >> Erm - surely I either need to set up my client to port-knock... which
> >> is a faff I'd rather avoid... in order to use the technique.
> >
> > nope. just start connection. wait a minute. cancel. start another one.
> > wait a minute. cancel. start new one - voila! :)
>
> Eeew... especially as this would apply to all connections - even the
> ones where I have a DSA key. I might be able to cope with this if it
> only applied to my initial connection, from which I could grab a copy of
> the DSA key.
Ok, let's theoreticise some more. My paranoia feels particularly frisky today,
so here it is:
remember, I've mentioned origianlly that once you authenticate successfully
once with DSA key - your IP is whitelisted. So subsequent connections go
right through.
> > well. Nobody but you knows your requiremens and specifics - we're just
> > listing options. It's up to you to either take 'em or leave 'em ;)
>
> Fair enough - but I've still not found an option for sharing/using
> shared block lists for bot-nets.
Open a Wiki page on Wikipedia, update it every so often and provide simple
parser for it so others can recycle same IPs. Since it's a Wiki page - others
can update it as well (including botnet owners, but then they'd have to
reveal themselves - tricky situation) :)
P.S.
I think I'd better stop with my mad science projects here before I go too far
and invent brand new theory on host protection ;)
--
Dmitry Makovey
Web Systems Administrator
Athabasca University
(780) 675-6245
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-12-04 15:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 20:02 [gentoo-user] Curious pattern in log files from ssh Steve
2008-12-03 20:16 ` [gentoo-user] " Nikos Chantziaras
2008-12-03 20:19 ` Paul Hartman
2008-12-03 20:52 ` Nikos Chantziaras
2008-12-03 20:17 ` [gentoo-user] " Albert Hopkins
2008-12-03 20:18 ` Paul Hartman
2008-12-03 20:49 ` Simon
2008-12-04 11:31 ` Steve
2008-12-05 7:16 ` Mick
2008-12-03 20:54 ` Alan McKinnon
2008-12-03 21:03 ` Dmitry S. Makovey
2008-12-03 21:47 ` Steve
2008-12-03 22:11 ` Dmitry S. Makovey
2008-12-03 22:55 ` Steve
2008-12-03 23:21 ` Paul Hartman
2008-12-03 23:46 ` Dmitry S. Makovey
2008-12-03 23:55 ` Steve
2008-12-04 0:07 ` Dmitry S. Makovey
2008-12-04 0:39 ` Steve
2008-12-04 15:50 ` Dmitry S. Makovey [this message]
2008-12-04 22:44 ` Adam Carter
2008-12-05 0:15 ` Dmitry S. Makovey
2008-12-04 23:42 ` Shawn Haggett
2008-12-03 22:54 ` Adam Carter
2008-12-04 11:24 ` Evgeniy Bushkov
2008-12-04 22:41 ` Adam Carter
2008-12-04 22:53 ` Adam Carter
2008-12-05 15:05 ` Evgeniy Bushkov
2008-12-07 5:52 ` Joshua Murphy
2008-12-04 19:03 ` Christian Franke
2008-12-04 20:22 ` Dmitry S. Makovey
2008-12-04 21:20 ` Alan McKinnon
2008-12-05 11:24 ` Steve
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=200812040850.31069.dmitry@athabascau.ca \
--to=dmitry@athabascau.ca \
--cc=Gentoo_sjh@shic.co.uk \
--cc=gentoo-user@lists.gentoo.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