public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OpenSSH security
Date: Tue, 7 Nov 2006 21:52:32 +0000	[thread overview]
Message-ID: <200611072152.44359.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4550E6DE.9070803@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]

On Tuesday 07 November 2006 20:04, Brian Davis wrote:
> In addition to fail2ban, look at deny2hosts and sshdfilter.
>
> fire-eyes wrote:
> > James Colby wrote:
> >> List members -
[snip]
> >> My Gentoo box is connected to a linksys router connected to my cable
> >> modem, the linksys is doing port forwarding to my gentoo box.  Also, I
> >> would like to avoid limiting which IP addresses can log into my SSH
> >> server

> > What you're seeing is a common, automated dictionary style attack. There
> > are several ways to get rid of them.
[snip]
> > The next less-simple way is to change the port sshd listens on. The
> > scripts assume the default of 22.

I use this as it is trivial to edit the sshd port No on /etc/ssh/sshd_config 
and /etc/ssh/ssh_config on the client.  However, you need to change the ssh 
client port back to 22 (or specify it on the command line) next time you 
connect to a production server.

> > The best way is to change the port sshd listens on, and also move to key
> > based authentication, and disable password based authentication. In this
> > way, even if they got the port, got a real user name, and had the right
> > password, it would not matter -- They haven't got the key.

I also use this option.  Dictionary attacks are totally ineffective as no user 
login passwds are accepted - full stop.  Only to add to the above that even 
if they have the private key, they will still need the secret passphrase to 
be able to use it.

You may also want to look in the wiki for port-knocking.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-11-07 22:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 19:51 [gentoo-user] OpenSSH security James Colby
2006-11-07 19:55 ` fire-eyes
2006-11-07 20:04   ` Brian Davis
2006-11-07 21:40     ` Pavel Sanda
2006-11-07 21:44       ` fire-eyes
2006-11-07 22:13         ` Mick
2006-11-07 21:52     ` Mick [this message]
2006-11-08  3:56       ` Jesper Fruergaard Andersen

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=200611072152.44359.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --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