full-disclosure - Re: targetted SSH bruteforce attacks

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-next>] [day] [month] [year] [list]

Message-Id: <20100617094439.5e40dfa8b2f4f620cdf199af6efb8890.e144f51270.wbe@email02.secureserver.net>
Date: Thu, 17 Jun 2010 09:44:39 -0700
From: <dink@...inkydink.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: targetted SSH bruteforce attacks

Point taken.  However, my ulterior motive was in promoting
obfuscated-openssh, which, IMHO, is an excellent and under-appreciated
enhancement to openssh.

Note that with iptables you can leave ssh on port 22 but have it answer
on other ports.  See http://proxyobsession.net/?p=869

Why anyone would want to do that is beyond me.

-------- Original Message --------
Subject: Re: [Full-disclosure] targetted SSH bruteforce attacks
From: Gary Baribault <gary@...ibault.net>
Date: Thu, June 17, 2010 8:44 am
To: full-disclosure@...ts.grok.org.uk

 I just knew that people would say that, and that's why I specified
 that I WANT to keep SSH on 22 .. it's fun to see the attacks, and it's
 interesting to see new types of attacks. The question here is whether
 anyone else is seeing such a targeted attack.

 Gary Baribault
 Courriel: gary@...ibault.net
 GPG Key: 0x685430d1
 Signature: 9E4D 1B7C CB9F 9239 11D9 71C3 6C35 C6B7 6854 30D1

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/