Re: HEAD's UP: possible 0day SSH exploit in the wild

[Clemens Pfaffinger <clpfaffinger@gmail.com>]

Hi,

this is standard for me. I always change the port of the openSSH-server.

My (current) solution is: 
Portsentry listens on port 22, while openSSH-server has another port.
Every port scan attempt will result in a ban via iptables and every 


connection to port 22 will also result in a ban via iptables.

Regards

________________________________________
Kontaktinformationen
clemens@csrv.at
www.cdev.at

2009/7/7 Clemens Pfaffinger <clpfaffinger@gmail.com>

Hi,

this is standard for me. I always change the port of the openSSH-server.

My (current) solution is:
Portsentry listens on port 22, while openSSH-server has another port.
Every port scan attempt will result in a ban via iptables and every
connection to port 22 will also result in a ban via iptables.

Regards

________________________________________
Kontaktinformationen
clemens@csrv.at
www.cdev.at

2009/7/7 Leandro Minatel <leandrominatel@gmail.com>

Hi,

a good practice, at least for me, is put openssh to listen in a different port than the default. I know, it's not the perfect solution.

Regards.