public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "James Homuth" <james@the-jdh.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: denyhosts quandry
Date: Fri, 20 Mar 2009 03:21:41 -0400	[thread overview]
Message-ID: <00c401c9a92c$848c4450$6400a8c0@quan> (raw)
In-Reply-To: <50FA21D3B04A453D9E9EA526C4282754@tdsdev>

Before you start looking for an app to blame, check the logs. Open a SSH
session, tail -F /bath/to/ssh.log, then load WinSCP. Then you'll know
precisely what's causing Denyhosts to freak out. 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Tyler Littlefield
Sent: March 19, 2009 10:26 PM
To: Speakup is a screen review system for Linux.
Subject: denyhosts quandry

Hello list,
I have a quick question.
I am running denyhosts on my linux system, to try to keep out attackers from
running a password cracker on my ssh.
It's caught a few, but it seems to be screaming when I log in with win SCP.
Basically, every time I log in, it just blocks my host out.
Is there a way I can either get it to stop, or possibly set it to not block
that host?
I'm not sure why WIN SCP would trigger a denyhosts, as as far as I know, it
runs when a password is incorrect.
Unless win SCP sends an invalid login for some reason first, or something of
that sort.


Thanks,
Tyler Littlefield
Web: tysdomain.com
email: tyler@tysdomain.com
My programs don't have bugs, they're called randomly added features.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


  parent reply	other threads:[~ UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Chris Brannon
   ` Tyler Littlefield
 ` James Homuth [this message]
   ` 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='00c401c9a92c$848c4450$6400a8c0@quan' \
    --to=james@the-jdh.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).