Home page logo

fulldisclosure logo Full Disclosure mailing list archives

Re: targetted SSH bruteforce attacks
From: <dink () mrhinkydink com>
Date: Thu, 17 Jun 2010 11:00:03 -0700

Um, yeah... that's exactly what I recommend in the article, which I'm
sure you read. ;o)

The original suggestion was "If you want SSH on a different port, do
this with firewall rules".

Way too much work, IMO.

-------- Original Message --------
Subject: Re: [Full-disclosure] targetted SSH bruteforce attacks
From: Michael Holstein <michael.holstein () csuohio edu>
Date: Thu, June 17, 2010 1:35 pm
To: dink () mrhinkydink com
Cc: full-disclosure () lists grok org uk

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


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/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]