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

Message-ID: <4C1A5CEE.80101@csuohio.edu>
Date: Thu, 17 Jun 2010 13:35:42 -0400
From: Michael Holstein <michael.holstein@...ohio.edu>
To: dink@...inkydink.com
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: targetted SSH bruteforce attacks

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

Or just change the entry in ./etc/sshd_config

# What ports, IPs and protocols we listen for
Port 22

>>From man(5)sshd_config :

Port:    Specifies the port number that sshd(8) listens on.  The default
is 22.  Multiple options of this type are permitted.  See also
ListenAddress.

Cheers,

Michael Holstein
Cleveland State University

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