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]

sshd does not start daemonized anymore

Subject: sshd does not start daemonized anymore
Date: Mon, 06 Feb 2006 12:58:15 +0100
Hi!

I have strange problem with my sshd (3.8.1p1.sarge.4) not starting daemonized anymore on a debian sarge system.

When starting with

   sshd -o "LogLevel DEBUG3"

it shows the following output and quits

   debug2: read_server_config: filename /etc/ssh/sshd_config
   debug1: sshd version OpenSSH_3.8.1p1 Debian-8.sarge.4
   debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key.
   debug1: read PEM private key done: type RSA
   debug1: private host key: #0 type 1 RSA
   debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key.
   debug1: read PEM private key done: type DSA
   debug1: private host key: #1 type 2 DSA


But when I start it with the "-ddd" option it starts well giving the following output and waiting for connections:


   debug2: read_server_config: filename /etc/ssh/sshd_config
   debug1: sshd version OpenSSH_3.8.1p1 Debian-8.sarge.4
   debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key.
   debug1: read PEM private key done: type RSA
   debug1: private host key: #0 type 1 RSA
   debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key.
   debug1: read PEM private key done: type DSA
   debug1: private host key: #1 type 2 DSA
   socket: Address family not supported by protocol
   debug1: Bind to port 22 on 0.0.0.0.
   Server listening on 0.0.0.0 port 22.

I have no clue what this could be since I'm pretty sure that I didn't change anything.

I removed ssh, purged all configuration data and reinstalled it without success.

What could this be?

Patrick

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