Home page logo

fulldisclosure logo Full Disclosure mailing list archives

RE: OpenSSH is a good choice?
From: Ron DuFresne <dufresne () winternet com>
Date: Tue, 21 Dec 2004 13:54:44 -0600 (CST)

On Tue, 21 Dec 2004, ALD, Aditya, Aditya Lalit Deshmukh wrote:

I am going to install OpenSSH in one of my servers, but I want to make
sure it is secure.
Does anybody know about vulnerabilites on OpenSSH, if yes, would you
like to suggest me another remote secure shell ?

There is a strong possibility that open port 22 will start attracting script
kiddies from the net like a dead animal attracts flies.....

Openssh or any version of ssh does not have any holes in it right now but
new holes are being discovered all the time. The best bet is to implement
some thing like port knocking to avoid this sort of direct expoosure to the
net or atleast run it on a non std port

the non std port advice is not worth much, security through obscurity
kinda thing.  Prot knocking can still discover the protocol on the
far end in many cases, with the proper tools.  Better yet, set limits as
to who can connect to the ssh port, in both /etc/hosts.allow <tcpd> and
your firewall rules.  Makes port knocking much less revealing and much
less a concern where sshd lives...

And while maintaining openssh, remember, you are also maintaining and
monitoring openssl for any issues as well.  So this needs to also be
processed in the monitor/patch maint cycles.


Ron DuFresne
"Sometimes you get the blues because your baby leaves you. Sometimes you get'em
'cause she comes back." --B.B. King
        ***testing, only testing, and damn good at it too!***

OK, so you're a Ph.D.  Just don't touch anything.

Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html

  By Date           By Thread  

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