[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ssh_key_type_from_name + old identity.pub
[Thread Prev] | [Thread Next]
- Subject: ssh_key_type_from_name + old identity.pub
- From: Martin Koller <kollix@xxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Fri, 30 May 2014 08:34:24 +0200
- To: libssh@xxxxxxxxxx
Hi, I'm analyzing a problem with the sftp KDE implementation as the sftp access to remote servers does no longer work. What I found out is that the problem lies in the implementation of the function ssh_key_type_from_name(), which does not detect correctly the keytype of my very old identity.pub file (from the year 2002). http://git.libssh.org/projects/libssh.git/tree/src/pki.c#n225 The identity.pub file content is: 1024 35 127039322722111462345444898295833032734724001755370075892619595922392229702202628069448938938754121637956908008581890704540298171311727563323302971541806845615265585131680856896693107049054716180460986201560348234339625510409796271930068304368440665402434317018435896073397995460767091056275814543809518806311 root@eiwnt048 the file is read inside ssh_pki_import_pubkey_file() and the keytype name is used as the first string in that file up to a blank character - which is here just the number "1024" It seems that it's not really a problem of the age of my file, since the command "ssh-keygen -t rsa1" still produces a similar file also starting with a number. Any idea what is the best way to solve this ? Either by fixing libssh or by changes on my side ? -- Best regards/Schöne Grüße Martin A: Because it breaks the logical sequence of discussion Q: Why is top posting bad? () ascii ribbon campaign - against html e-mail /\ - against proprietary attachments Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at
Re: ssh_key_type_from_name + old identity.pub | Andreas Schneider <asn@xxxxxxxxxxxxxx> |