All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Michael Rash <mbr@cipherdyne.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: SSHBrute Force: False Postives
Date: Fri, 2 Feb 2007 12:26:54 -0500	[thread overview]
Message-ID: <20070202172654.GA24236@animx.eu.org> (raw)
In-Reply-To: <20070202143815.GA30820@minastirith>

Michael Rash wrote:
> > franck joncourt wrote:
> > > In order to prevent such attacks, you can write iptables rules to set up port knocking. This is the way, I do.
> > 
> > I thought about doing this, but I ultimately decided against it.  The
> > problems of doing the knocking outweighted the benefits.  I prefer to let
> > them try a few times before my current rules ban them.
> 
> If someone finds a remote exploit in sshd, then just allowing
> connections at all can potentially expose you to compromise.  As far as

True.

> port knocking is concerned, I agree, there are a ton of problems.  There
> is a better alternative called Single Packet Authorization:
> 
> http://www.cipherdyne.org/fwknop/docs/SPA.html
> 
> Fwknop is an implementation that is based around iptables:
> 
> http://www.cipherdyne.org/fwknop/

This still means that all authorized users have to do this which is not what
I want to do.  What if I'm at someone's house and decide I want in to my
system and they don't have any way of performing the port knocking or the
fwknop.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


  reply	other threads:[~2007-02-02 17:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2007-02-01  1:28 Lpct

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=20070202172654.GA24236@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=mbr@cipherdyne.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.