AbcLinuxu:/ Poradna / Linuxová poradna / SSH klient problem

Štítky: bezpečnost, Debian, distribuce, Internet, KDE, práva, software, SSH, SSL, šifrování, textové editory, Vim

Dotaz: SSH klient problem

16.1.2005 22:49 Marek Borůvka
SSH klient problem

Přečteno: 399×

Odpovědět | Admin

Ahoj resim takovy zajimavy problem s SSH klientem: Z inkriminovaneho serveru se nejsem schopen pripojit na zadnou masinu pres SSH. Na server se muzu normalne pres ssh pripojit tedy demon SSHD bezi v pohode. Nicmene kdyz se ze serveru snazim pripojita na nejaky dalsi linuxbox tak to vypise tuto hlasku: HOST VERIFICATION FAILED. Zkousel jsem uz smazat vsechny konfiguraky od SSH, klice atd, reinstalaci OpenSSH,rekompilaci OpenSSH a vzdy je to stejne. Jeste bych chtel upozornit ze se jedna o zrcadlovou kopii serveru na kterem je VSE OK (ke kopii pouzito mondo). Akorat na puvodnim serveru je jadro 2.4.24 a na novem je 2.6.10 . Jedna se o Slack 10. Tady je vypis z STDOUT

root@samba:~# ssh 10.154.82.1 -v
OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 10.154.82.1 [10.154.82.1] port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.8.1p1
debug1: match: OpenSSH_3.8.1p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
Host key verification failed.

Uz si s tim nevim rady diky za kazde nakopnuti.

Nástroje: Začni sledovat (0) ?

Odpovědi

16.1.2005 22:54 Petr
Rozbalit Rozbalit vše Re: SSH klient problem

Rekl bych, ze v te hlasce je dulezite slovo key. Jinak receno, nejspis ti nesouhlasi klice. (verejny klic serveru, a klic, ktery mas ulozeny v ~/.ssh/know_hosts)
PS: Zkus pro ten vypis priste pouzit tagy pre

16.1.2005 23:01 Marek Borůvka
Rozbalit Rozbalit vše Re: SSH klient problem

Vim vypada to tak , ale neni to tento problem.

Known hosts jse promazal (ten byl jeste z puvodniho serveru) ale nepomaha to. Nove klice se do toho souboru ani nemaji tendencdi ukladat. Navic to delaji VESKERE servery na ktere se pripojuju. Proste tohle sem jeste nevidel.... A kolegove mi taky neporadili tak to zkousim tady

16.1.2005 23:18 Jarek Šeděnka
Rozbalit Rozbalit vše Re: SSH klient problem

zkus tam dat vice -v (myslim, ze ssh snese az ssh nekam -v -v -v :-)

, pak to treba rekne vice..

17.1.2005 00:17 Marek Borůvka
Rozbalit Rozbalit vše Re: SSH klient problem

Takze jsem zkompiloval nove ssl + nove ssh, vygeneroval klice a jsem tam kde sem byl :) tady je vypis

root@samba:~/.ssh# ssh 10.154.83.1 -vvvv
OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004
debug2: ssh_connect: needpriv 0
debug1: Connecting to 10.154.83.1 [10.154.83.1] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type 0
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3
debug1: match: OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.9p1
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 123/256
debug2: bits set: 508/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: filename /etc/ssh/ssh_known_hosts
debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: filename /etc/ssh/ssh_known_hosts
debug2: no key of type 0 for host 10.154.83.1
debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts2
debug3: check_host_in_hostfile: filename /etc/ssh/ssh_known_hosts2
debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: filename /etc/ssh/ssh_known_hosts
debug2: no key of type 2 for host 10.154.83.1
Host key verification failed.
root@samba:~/.ssh#

17.1.2005 00:25 jm
Rozbalit Rozbalit vše Re: SSH klient problem

Je vubec zakompilovana podpora potrebneho sifrovani v jadre? Pokud se ty stroje nelisi nicim jinym, tak to je IMHO jedina moznost.

25.4.2005 12:16 Nafe
Rozbalit Rozbalit vše Re: SSH klient problem

Narazil jsem dnes na stejny problem, vysledekm patrani byla spatna prava v /dev/tty Spravna prava -
crw-rw-rw- 1 root tty 5, 0 2005-04-25 12:15 /dev/tty

25.4.2005 13:52 Michal Marek (twofish) | skóre: 55 | blog: { display: blog; } | Praha
Rozbalit Rozbalit vše Re: SSH klient problem

Asi je v konfiguráku klienta

StrictHostKeyChecking yes

takže se nepřipojí v serverům, které nezná.

Založit nové vlákno • Nahoru

Tiskni Sdílej: