[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ssh_key_type_from_name + old identity.pub
[Thread Prev] | [Thread Next]
[Date Prev] | [Date Next]
- Subject: Re: ssh_key_type_from_name + old identity.pub
- From: Andreas Schneider <asn@xxxxxxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Fri, 30 May 2014 13:01:13 +0200
- To: libssh@xxxxxxxxxx
On Friday 30 May 2014 08:34:24 Martin Koller wrote: > 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 > 127039322722111462345444898295833032734724001755370075892619595922392229702 > 2026280694489389387541216379569080085818907045402981713117275633233029715418 > 0684561526558513168085689669310704905471618046098620156034823433962551040979 > 6271930068304368440665402434317018435896073397995460767091056275814543809518 > 806311 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 ? We should fix it in libssh and you should stop using rsa1 keys ;) -- andreas -- Andreas Schneider GPG-ID: CC014E3D www.cryptomilk.org asn@xxxxxxxxxxxxxx
ssh_key_type_from_name + old identity.pub | Martin Koller <kollix@xxxxxx> |