From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: denyhosts quandry
Date: Thu, 19 Mar 2009 20:47:35 -0600 [thread overview]
Message-ID: <5AEE60B435E84DD69C7194E9D481EFC9@tdsdev> (raw)
In-Reply-To: <20090320024145.VCR21373.eastrmmtao103.cox.net@eastrmimpo03.cox.net>
that would kill win SCP, which is my local editor, or I'd be up for that.
Thanks,
Tyler Littlefield
Web: tysdomain.com
email: tyler@tysdomain.com
My programs don't have bugs, they're called randomly added features.
----- Original Message -----
From: "Chris Brannon" <cmbrannon@cox.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, March 19, 2009 8:42 PM
Subject: Re: denyhosts quandry
>> I am running denyhosts on my linux system, to try to keep out attackers
>> from
>> running a password cracker on my ssh.
>
> There is a really easy way to protect ssh from password attacks.
> Only allow public-key authentication.
> Require that people authenticate with a key when connecting, and disallow
> password-based authentication.
> See your local ssh_config manpage.
>
> -- Chris
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Chris Brannon
` Tyler Littlefield [this message]
` James Homuth
` Kirk Reiser
` Tom Moore
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` farhan
` Gregory Nowak
` Gregory Nowak
` Tyler Littlefield
` Tyler Littlefield
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` Jayson Smith
` Tyler Littlefield
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=5AEE60B435E84DD69C7194E9D481EFC9@tdsdev \
--to=tyler@tysdomain.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).