View Single Post
Old 07-11-2012, 01:03 PM   #10
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Unless the K3 SSH server is completely different from K5, you'll want to look for documentation about dropbear, not openssh.

On the K5, the file you would be looking for is /usr/local/etc/dropbear/dropbear_rsa_host_key . On the K3, the path is probably different, but the file name might be the same.

You should also be aware that the file formats of putty, openssh, and dropbear are all different. For dropbear, check dropbearconvert, for putty, I don't remember the tool's name.

IMO, what you're trying to do is actually not worth the hassle. Delete all client-side "known keys" for the device, then connect via USB, then via Wifi. (Write down the key that you got, if you're really paranoid). If that key ever changes in the future, your SSH client should warn you.

Last edited by ixtab; 07-11-2012 at 01:11 PM.
ixtab is offline   Reply With Quote