From: franck <joncourt_franck@yahoo.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: SSHBrute Force: False Postives
Date: Tue, 06 Feb 2007 22:12:06 +0100 [thread overview]
Message-ID: <45C8EF26.40506@yahoo.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0702061552320.3777@darkstar.sysinfo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
R. DuFresne wrote:
> portknocking is merely security through obscurity, is it not?
>
> especially so with modules that reside with preset defaults...
>
> Thanks,
>
> Ron DuFresne
According to me, changing SSH default port is obscurity, and is not more
secure ; Port knocking is more about preventing people from gaining
access to your machine by improving authentication process, that's it.
- --
Franck Joncourt
http://www.debian.org
http://smhteam.info/wiki/
GPG server : pgpkeys.mit.edu
Fingerprint : C10E D1D0 EF70 0A2A CACF 9A3C C490 534E 75C0 89FE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFyO8mxJBTTnXAif4RAuxjAJ9IHjWPv4QfKOOiuXLkzSu8bntz3ACfe+ne
BXp0qd1XR73lviZ7NMvBnYs=
=WjOM
-----END PGP SIGNATURE-----
___________________________________________________________
Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
next prev parent reply other threads:[~2007-02-06 21:12 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
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 [this message]
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=45C8EF26.40506@yahoo.co.uk \
--to=joncourt_franck@yahoo.co.uk \
--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.