full-disclosure - reduction of brute force login attempts via SSH through iptables --hashlimit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Thu Mar  2 17:18:54 2006
From: gautam.bipin at gmail.com (Bipin Gautam)
Subject: reduction of brute force login attempts via SSH
	through iptables --hashlimit

yeh, common dude he just avoided a problem or was it a intentional
backdoor? A better way could be blocking the rate of no of SYN to port
22 by iptables form any IP itself. (yeh, whitelist few first)

see thats the reason to use KEY instead of passwd.

On 3/1/06, GroundZero Security <fd@....org> wrote:
> well i somehow felt someone will be pedantic over it.
> its a quick script originally thrown together in a few minutes for personal use and wasn't really
> intended to be released, i just thought it may help someone.
> besides that this is ment to stop those bruteforce attempts which *all* have more than
> enough users without spaces they try. or do you know anyone that does ssh bruteforce by hand?
> you may be able to add a bogus ip (wow your l33t), but it wouldnt be of any use so...
> instead of beeing a smartass why dont you provide a better solution for the people who are annoyed by
> those bruteforce attacks?
>

--

Bipin Gautam
http://bipin.tk

Zeroth law of security: The possibility of poking a system from lower
privilege is zero unless & until there is possibility of direct,
indirect or consequential communication between the two...