Portál AbcLinuxu, 10. května 2025 06:31

Dotaz: SSH - spatna passphrase, nebo klic?

30.6.2006 09:10 :-)
SSH - spatna passphrase, nebo klic?
Přečteno: 373×
Odpovědět | Admin
Ahoj.

Nelze se pripojit pres ssh na sever. Z Windows, kde byly klice vygenerovany to jde. Z FreeBSD vsak jiz nikoliv.

passphrase zadavam spravne

Dekuji Vam.


Nize je: ssh smudla -vvv -i /root/.ssh/mujklic
----

OpenSSH_4.2p1 FreeBSD-20050903, OpenSSL 0.9.7e-p1 25 Oct 2004
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to smudla.cz [192.168.2.1] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug3: Not a RSA1 key file /root/.ssh/mujklic.
debug2: key_type_from_name: unknown key type '----'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Comment:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '----'
debug3: key_read: missing keytype
debug1: identity file /root/.ssh/mujklic type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.6.1p1
debug1: match: OpenSSH_3.6.1p1 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.2p1 FreeBSD-20050903
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-hellma n-group1-sha1
debug2: kex_parse_kexinit: ssh-dss,ssh-rsa
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,a es192-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,arcfour128,arcfour256,arcfour,a es192-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,hm ac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hm ac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,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-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r ijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r ijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hm ac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hm ac-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: 127/256
debug2: bits set: 502/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: match line 2
debug1: Host 'smudla.cz' is known and matches the DSA host key.
debug1: Found key in /root/.ssh/known_hosts:2
debug2: bits set: 524/1024
debug1: ssh_dss_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /root/.ssh/mujklic (0x0)
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/mujklic
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type -unknown
Enter passphrase for key '/root/.ssh/mujklic':
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type -unknown
debug2: bad passphrase given, try again...
Enter passphrase for key '/root/.ssh/mujklic':
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type -unknown
debug2: bad passphrase given, try again...
Enter passphrase for key '/root/.ssh/mujklic':
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type -unknown
debug2: bad passphrase given, try again...
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).

Nástroje: Začni sledovat (0) ?Zašle upozornění na váš email při vložení nového komentáře.

Odpovědi

Jiří Poláček avatar 30.6.2006 10:22 Jiří Poláček | skóre: 47 | blog: naopak | Sivice
Rozbalit Rozbalit vše Re: SSH - spatna passphrase, nebo klic?
Odpovědět | | Sbalit | Link | Blokovat | Admin
Zjevně ten soubor s klíčem je vadný. Není problém s jiným typem konce řádků?
Sudoku omrzelo? Zkuste bobblemaze! | Statistiky jsou jak bikiny. Napoví hodně, všechno ale neukážou.
30.6.2006 10:28 :-)
Rozbalit Rozbalit vše Re: SSH - spatna passphrase, nebo klic?
Je to mozne, mam zkusit nejak ty radky v klici upravit?

Tusite, jak na to?

Dekuji moc...
30.6.2006 12:17 JirkaV
Rozbalit Rozbalit vše Re: SSH - spatna passphrase, nebo klic?
Problem je ve formatu souboru. Format se da zmenit prikazem ssh-keygen na tom FreeBSD, myslim ze spravna syntaxe by mohla byt "ssh-keygen -i -f soubor_s_klicem_s_windows > novy_soubor"
30.6.2006 12:30 :-)
Rozbalit Rozbalit vše Re: SSH - spatna passphrase, nebo klic?
Pise to:


# ssh-keygen -i -f /root/.ssh/mujklic > FreeBSD_klic
unsupported cipher 3des-cbc
decode blob failed.
#


Jinak to mam v RSA 1024 :-)
30.6.2006 12:59 JirkaV
Rozbalit Rozbalit vše Re: SSH - spatna passphrase, nebo klic?
Odpovědět | | Sbalit | Link | Blokovat | Admin
Hm, to skoro vypada ze na tom FreeBSD je stara verze OpenSSH :)

Co to udelat jinak? Vygenerovat si na FreeBSD jiny par klicu a ten verejny pak hodit na ten cilovy server? Mit dva (a vice) klicu na cilovem stroji neni problem...

Asi je to jednodussi reseni nez laborovat s ruznymi formaty/siframi
30.6.2006 13:09 :-)
Rozbalit Rozbalit vše Re: SSH - spatna passphrase, nebo klic?
Myslim, ze to tak udelam a bude to "vyrizene" :-)

Dekuji Vam za Vas cas :-)

Založit nové vláknoNahoru

Tiskni Sdílej: Linkuj Jaggni to Vybrali.sme.sk Google Del.icio.us Facebook

ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.