Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Making sshd_config not world readable

Subject: Re: Making sshd_config not world readable
Date: Mon, 28 Mar 2005 11:54:06 -0500
On Mon, Mar 28, 2005 at 03:17:02PM +0100, Miguel Saturnino wrote:
What are the drawbacks of making sshd_config not world readable, like
this:
[SNIP]
In the man page says it is not necessary that the file be world readable
but it is recommended... I don't want it to be world readable so that
regular users don't know what Port and ListenAddress sshd is using.

If protecting this information is the only reason you want to make the
file inaccessible, it may be a waste of your time.  For example, on
some systems, "netstat -pant" may show them which programs are
listening on what TCP ports.  It won't work on recent Linux systems,
but it did work on certain versions of Linux, and may work on other
operating systems.

The users could also run nmap on the machine to scan every port,
which may reveal where ssh is running.

-- 
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D

Attachment: pgpLjnHzrFVlT.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>