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]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

sshd cannot be started normally after system crash

from [Eddie] Network Security [Permanent Link]
Subject: sshd cannot be started normally after system crash
Date: Fri, 28 Apr 2006 11:22:17 +0800 
Hi all,

Please help, I cannot use ssh to connect to the machine shown below
after a system crash.

My system environment is
SuSE SLES 9 SP2 on ppc64
2.6.5-7.191-pseries64
openssh-3.8p1-37.17

when I start sshd, the messages are
client1a:~ # /etc/init.d/sshd start
Starting SSH daemonfree(): invalid pointer 0x10063e30!
free(): invalid pointer 0x100640d8!
key_load_private_rsa1: RSA_blinding_on failed
Could not load host key: /etc/ssh/ssh_host_key
free(): invalid pointer 0x100645f8!
key_load_private_pem: RSA_blinding_on failed
Could not load host key: /etc/ssh/ssh_host_rsa_key
Disabling protocol version 1. Could not load host key
                                                                      
                                         done

no response when running
client1a:~ # ssh localhost

logs in /var/log/messages
Apr 28 10:30:30 client1a sshd[6896]: debug1: Bind to port 22 on ::.
Apr 28 10:30:30 client1a sshd[6896]: Server listening on :: port 22.
Apr 28 10:30:50 client1a sshd[6896]: debug1: Forked child 6934.
Apr 28 10:30:50 client1a sshd[6934]: Connection from ::ffff:127.0.0.1 port 32780
Apr 28 10:30:50 client1a sshd[6934]: debug1: Client protocol version
2.0; client software version OpenSSH_3.8p1
Apr 28 10:30:50 client1a sshd[6934]: debug1: match: OpenSSH_3.8p1 pat OpenSSH*
Apr 28 10:30:50 client1a sshd[6934]: debug1: Enabling compatibility
mode for protocol 2.0
Apr 28 10:30:50 client1a sshd[6934]: debug1: Local version string
SSH-2.0-OpenSSH_3.8p1
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 4
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 5
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 6
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 7
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 8
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 9
...
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 182
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 183
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 184
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 185
Apr 28 10:30:50 client1a sshd[6934]: error: Bad prime description in line 186
Apr 28 10:30:50 client1a sshd[6934]: WARNING: no suitable primes in
/etc/ssh/primes

Thanks a lot

Regards,
Eddie
[More messages with this same subject...]




<Prev in Thread] Current Thread [Next in Thread>
  • sshd cannot be started normally after system crash, Eddie <=
Previous by Date:  Announce: X.509 certificates support in OpenSSH version 5.4, Roumen Petrov
Next by Date:  Re: permission denied (publickey), Eni
Previous by Thread:  Announce: X.509 certificates support in OpenSSH version 5.4, Roumen Petrov
Indexes:  [Date] [Thread] [Top] [All Lists]