Re: [Full-disclosure] SSH Bruteforce blocking script

2005-09-06 Thread miah
, September 02, 2005 11:56 PM To: full-disclosure@lists.grok.org.uk Subject: Re: [Full-disclosure] SSH Bruteforce blocking script If you're running iptables why not make use of hashlimit? Once a limit is reached all connection attempts from that IP would be blocked until the hash entry expires

RE: [Full-disclosure] SSH Bruteforce blocking script

2005-09-06 Thread Ron DuFresne
- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of miah Sent: Friday, September 02, 2005 11:56 PM To: full-disclosure@lists.grok.org.uk Subject: Re: [Full-disclosure] SSH Bruteforce blocking script If you're running iptables why not make use of hashlimit? Once a limit

RE: [Full-disclosure] SSH Bruteforce blocking script

2005-09-04 Thread Michael L Benjamin
] On Behalf Of miah Sent: Friday, September 02, 2005 11:56 PM To: full-disclosure@lists.grok.org.uk Subject: Re: [Full-disclosure] SSH Bruteforce blocking script If you're running iptables why not make use of hashlimit? Once a limit is reached all connection attempts from that IP would be blocked until

FW: [Full-disclosure] SSH Bruteforce blocking script

2005-09-04 Thread Michael L Benjamin
-Original Message- From: francisco [mailto:[EMAIL PROTECTED] Sent: Sunday, September 04, 2005 01:49 AM To: Michael L Benjamin Subject: RE: [Full-disclosure] SSH Bruteforce blocking script On Fri, 2 Sep 2005, Michael L Benjamin wrote: It's an idea. Involves calling another

FW: [Full-disclosure] SSH Bruteforce blocking script

2005-09-04 Thread Michael L Benjamin
-Original Message- From: Michael L Benjamin Sent: Monday, September 05, 2005 12:04 PM To: 'Gerald Holl' Subject: RE: [Full-disclosure] SSH Bruteforce blocking script Thank you. Yes, I've used a similar script in the past to block hosts from Apache log output. This does have it's

Re: [Full-disclosure] SSH Bruteforce blocking script

2005-09-03 Thread Gerald Holl
On 2005-09-02 09:37, Michael L Benjamin wrote: Here is a simple script I've coded up that I use on 3 of my RedHat Enterprise Linux 3 (RHEL3) servers. I decided to do this after seeing the amount of activity from places like China/Korea/Taiwan in relation to SSH brute force probes. I'll throw

[Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Michael L Benjamin
Hi there, Here is a simplescript I've coded up that I use on 3 of my RedHat Enterprise Linux 3 (RHEL3) servers. I decided to do this after seeing the amount of activity from places like China/Korea/Taiwan in relation to SSH brute force probes. I'll throw it open here for

Re: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Alejandro Barrera
Well, we apreciate your script although I would preffer to stay with my nice bruteforcing attempts than to create an insecure temporary file bug: [EMAIL PROTECTED]:~$ cat test.sh #!/bin/sh SCRIPT_NAME=$(basename $0) TMP_FILE=/tmp/${SCRIPT_NAME}.$$ touch ${TMP_FILE} echo pwn3d ${TMP_FILE} exit

RE: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Michael L Benjamin
back to that later. Thanks for your input. Cheers, Mike. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alejandro Barrera Sent: Friday, September 02, 2005 04:04 PM To: full-disclosure@lists.grok.org.uk Subject: Re: [Full-disclosure] SSH Bruteforce

Re: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Christoph Moench-Tegeder
## Michael L Benjamin ([EMAIL PROTECTED]): TMP_FILE=/tmp/${SCRIPT_NAME}.$$ Considerd mktemp(1)? Regards, Christoph -- Spare Space ___ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and

RE: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Michael L Benjamin
-Tegeder Sent: Friday, September 02, 2005 05:05 PM To: full-disclosure@lists.grok.org.uk Subject: Re: [Full-disclosure] SSH Bruteforce blocking script ## Michael L Benjamin ([EMAIL PROTECTED]): TMP_FILE=/tmp/${SCRIPT_NAME}.$$ Considerd mktemp(1)? Regards, Christoph -- Spare Space

Re: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Christoph Moench-Tegeder
## Michael L Benjamin ([EMAIL PROTECTED]): Involves calling another process though. Not worse than using touch/chmod/chown. And much better than just hoping that everything will be alright :) I think the shell has enough tools to adequately create a secure temp file if I go about it in the

Re: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Pedro Hugo
Hi, I don't want to debate the goodness or badness of the strategy of blocking hosts like this in /etc/hosts.deny. It works perfectly for me, and most likely would for you, so no religious debates thanks. It's effective at blocking bruteforce attacks. If a host EXCEEDS a specified number of

RE: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread Michael L Benjamin
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pedro Hugo Sent: Friday, 2 September 2005 05:53 PM To: full-disclosure@lists.grok.org.uk Subject: Re: [Full-disclosure] SSH Bruteforce blocking script Hi, I don't want to debate the goodness or badness

Re: [Full-disclosure] SSH Bruteforce blocking script

2005-09-02 Thread miah
: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pedro Hugo Sent: Friday, 2 September 2005 05:53 PM To: full-disclosure@lists.grok.org.uk Subject: Re: [Full-disclosure] SSH Bruteforce blocking script Hi, I don't want to debate the goodness