From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: denyhosts quandry
Date: Fri, 20 Mar 2009 08:57:24 -0600 [thread overview]
Message-ID: <D65A227B5FED4898BA08D2B1CFBDE345@tdsdev> (raw)
In-Reply-To: <016701c9a96b$e2937840$6400a8c0@quan>
>That, plus sometimes,
>it's just fun to recompile.
I scream and throw a fit every time I have to recompile. :) actually I like
changing configuration around, I really scream when it breaks and I see the
lovely "segmentation fault." :)
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: "James Homuth" <james@the-jdh.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Sent: Friday, March 20, 2009 8:55 AM
Subject: RE: denyhosts quandry
> There's probably a configuration directive you can change to turn it off,
> even if it *is* listed as a dependancy. But Gentoo gives me that level of
> customization, so I figure I might as well use it. That, plus sometimes,
> it's just fun to recompile.
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca
> [mailto:speakup-bounces@braille.uwo.ca]
> On Behalf Of Tyler Littlefield
> Sent: March 20, 2009 10:49 AM
> To: Speakup is a screen review system for Linux.
> Subject: Re: denyhosts quandry
>
> nice. I hadn't had that issue, but then again my apt-get does it all for
> me.
>
> I'm not pacient enough to sit there and wait for openSSH to compile and
> fight with it on something like slackware, though it would probably be
> the
> prefered method of configuring things. Then I wouldn't be at the mercy of
> the package maintainers.
>
>
>
> 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: "James Homuth" <james@the-jdh.com>
> To: "'Speakup is a screen review system for Linux.'"
> <speakup@braille.uwo.ca>
> Sent: Friday, March 20, 2009 8:44 AM
> Subject: RE: denyhosts quandry
>
>
>> It doesn't help much. Mine, at least, wouldn't stop asking for a password
>> even if I set SSHD to ask for public key only. So rather than fight with
>> it,
>> I recompiled OpenSSH without it.
>>
>> -----Original Message-----
>> From: speakup-bounces@braille.uwo.ca
>> [mailto:speakup-bounces@braille.uwo.ca]
>> On Behalf Of Tyler Littlefield
>> Sent: March 20, 2009 10:03 AM
>> To: Speakup is a screen review system for Linux.
>> Subject: Re: denyhosts quandry
>>
>> started removing pam? >.>
>> I've found it has helped me in locking down on security, though I'm not
>> really sure by how much.
>>
>>
>> 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: "James Homuth" <james@the-jdh.com>
>> To: "'Speakup is a screen review system for Linux.'"
>> <speakup@braille.uwo.ca>
>> Sent: Friday, March 20, 2009 7:53 AM
>> Subject: RE: denyhosts quandry
>>
>>
>>> Fail2Ban operates along the same theory as Denyhosts, though. So
>>> whatever
>>> regular expression causes Denyhosts to flip out will probably do the
>>> same
>>> for Fail2ban. Tried it on my Gentoo boxes a while back and noticed very
>>> little if any difference. So instead I switched back to Denyhosts and
>>> started removing PAM from my system.
>>>
>>> -----Original Message-----
>>> From: speakup-bounces@braille.uwo.ca
>>> [mailto:speakup-bounces@braille.uwo.ca]
>>> On Behalf Of Kirk Reiser
>>> Sent: March 20, 2009 8:58 AM
>>> To: Speakup is a screen review system for Linux.
>>> Subject: Re: denyhosts quandry
>>>
>>> A package I just recently found and have installed on a couple of
>>> systems
>>> is
>>> fail2ban which has a bunch of popular rule sets included and is easily
>>> expandable by the user. Basically it parses your systems logs and then
>>> performas ip blocks with iptables based on your specifications. It has
>>> ssh
>>> buffer overrun pertection built-in by default. It also has others you
>>> can
>>> easily enable. There's a debian package so I imagine there are packages
>>> available for other distro's as well.
>>>
>>> Kirk
>>> --
>>> Kirk Reiser The Computer Braille Facility
>>> e-mail: kirk@braille.uwo.ca University of Western Ontario
>>> phone: (519) 661-3061
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> 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
` James Homuth
` Kirk Reiser
` Tom Moore
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield
` James Homuth
` Tyler Littlefield [this message]
` 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=D65A227B5FED4898BA08D2B1CFBDE345@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).