OpenSSH Host Key Verification Failed

GodSendDeath · 11-08-2004, 10:22 PM

Hey everyone,

I used to be able to SSH to local computers and to my school computers without a problem. But out of nowehere, I got this error stating "host key verification failed:

godsenddeath@linux# ssh -l godsenddeath -vvv 192.168.1.100

produces....

.................
debug2: dh_gen_key: priv key bits set: 125/256
debug2: bits set: 539/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /home/godsenddeath/.ssh/known_hosts
debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts
debug3: check_host_in_hostfile: filename /home/godsenddeath/.ssh/known_hosts
debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts
debug2: no key of type 0 for host 192.168.1.100
debug3: check_host_in_hostfile: filename /home/godsenddeath/.ssh/known_hosts2
debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts2
debug3: check_host_in_hostfile: filename /home/godsenddeath/.ssh/known_hosts
debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts
debug2: no key of type 1 for host 192.168.1.100
ssh_askpass: exec(/usr/local/libexec/ssh-askpass): No such file or directory
Host key verification failed.
................

I tried "ssh-keygen -t rsa" to reproduce keys, ive tried deleteing config files. This has happend on another computer but I just decided to reinstall linux, which is a poor windows-like solution. If anyone has any ideas, please respond. If any further information is needed, i will post!

-GSD

GodSendDeath · 11-08-2004, 10:24 PM

Also, at the same time, my man pages wont work. Im not 100% sure if the problems are related, but they all seemed to happen at the same time. For example

godsenddeath@Slayer:~$ man ls
Error executing formatting or display command.
System command (cd /usr/man && (echo ".ll 9.1i"; echo ".pl 1100i"; /bin/gunzip -c '/usr/man/man1/ls.1.gz'; echo ".\\\""; echo ".pl \n(nlu+10") | /usr/bin/gtbl | /usr/bin/nroff -S -mandoc | /usr/bin/less -is) exited with status 256.
No manual entry for ls
.................

Note: I am more focused on the SSH issue, but I figured this occurance might lead to some information.

-GSD

dezza · 11-09-2004, 03:01 AM

I looks like OpenSSH ain't installed probally, try recompiling/installing it ..

GodSendDeath · 11-09-2004, 08:20 PM

I already tried grabbing the latest sources and installed. Still no luck. I still have no idea why its doing this. Please keep the responses coming guys. Thank you

Specs:

Kernal 2.6.7
Slackware 10

karlan · 11-16-2004, 08:35 PM

i'm having these same man pages problems, i'm trying to figure out what it is. btw i'm slackware 10

karlan · 11-17-2004, 12:16 AM

I kinda solved it, ghetto hack style.

1) move /usr/bin/man to /usr/bin/man.broken
2) create exectuable, empty, file /usr/bin/man
3) fill /usr/bin/man with the following code:

Code:

#!/bin/bash
for i in 1 2 3 4 5 6 7 8 9
do

if [ -f "/usr/man/man$i/$1.$i.gz" ]; then
  echo "Read $1($i)?"
  read choice
  if [ "$choice" = "y" -o "$choice" = "Y" ] ; then
     (cd /usr/man && (echo ".ll 9.1i"; echo ".pl 1100i"; /bin/gunzip -c "/usr/man/man$i/$1.$i.gz"; echo ".\\\""; echo ".pl \n(nlu+10") | /usr/bin/gtbl| /usr/bin/nroff -S -mandoc | more )
  fi
else
    echo "No /usr/man/man$i/$1.$i.gz. . ."
fi


done

Its not a full replacement, but it works

GodSendDeath · 11-17-2004, 09:23 PM

I just wanted to post that I reinstalled Slackware Linux using the 2.6.7 kernel instead of the 2.6.9. I believe I posted earlier that I'm using the 2.6.7 kernel, when I was in fact using 2.6.9. Im not sure why a newer kernel would affect man pages behavior or SSH behavior. Regardless, I've just given up on the problem and plan on not upgrading kernels for a while. Thanks for everyones participation

-GSD

sinistre · 11-27-2004, 05:13 PM

Read somewhere that it would work if you upgraded the makedev package. I have one box with Slack10 which works fine (which is upgraded with slackgrade) and one where it doesn't work -- where I am upgrading as I'm typing this. Try upgrading!

Oh btw I have the latest kernel on both.

masand · 01-20-2005, 11:32 PM

hi
i am too having the same problem
i am using a custom 2.6.10 kernel on slakware 10.0

is that a problem???

regards

jschiwal · 01-20-2005, 11:57 PM

I have some Ideas on the ssh problem. If either an IP address changed on a host, or the keys were replaced, or the ~/.known_hosts file has global permissions, you will have a problem connecting.

First make sure that the permissions of the config files in ~/.ssh wheren't changed to allow global reading. If they were, you will want to re-generate a key pair.

Second, try deleting the entry in ~/.ssh/known_hosts on both computers and make the connection anew.

A third thing to try is to add the public key to the remote computer to the ~/.ssh/authorized_keys. The public key is probably saved as ~/.ssh/identity.pub

This will allow you to perform passwordless logins, and avoids the transmission of the encrypted password.

masand · 01-21-2005, 01:15 AM

hey the kernel is the problem in my case

when i use the default kernel it goes fine
but when i use my own custom built 2.6.10 kernel i have problem with SSH and man pages

wonder what is the solutiuon to this

regards

sinistre · 01-21-2005, 12:07 PM

Have you tried doing as I suggested? Upgrading using slackgrade fixed this problem for me.

masand · 01-21-2005, 12:28 PM

this thread helped me

http://www.linuxquestions.org/questi...hreadid=245456

regards