MudaliarArun / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
0 stars 0 forks source link

After phone wipe, connectbot will no longer import keys #189

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
After a phone (G1) wipe and reload, and reinstallation of connectbot, the 
program will no longer import new keys (though it will generate new ones 
of its own).  The private key in question is on the SD card as always, but 
when the import key function is used the system text editor opens!  I've 
found no way around this so far, and viewing the key in the text editor is 
merely frustrating.

Original issue reported on code.google.com by lauren4...@gmail.com on 28 Aug 2009 at 8:07

GoogleCodeExporter commented 8 years ago
I suppose you installed a file manager? Which one?

Original comment by kenny@the-b.org on 28 Aug 2009 at 12:25

GoogleCodeExporter commented 8 years ago
Hmm.  I have several, but most recent was ASTRO.  I have the Linda File Manager 
in 
there also.  Thanks.

Original comment by p...@pfir.org on 28 Aug 2009 at 3:54

GoogleCodeExporter commented 8 years ago
I should add, I don't have to import many keys, so if there's a practical 
workaround 
so I can get my current key in, that would be a big help.  Thanks.

Original comment by lauren4...@gmail.com on 28 Aug 2009 at 8:08

GoogleCodeExporter commented 8 years ago
I have now removed my two file managers, removed connectbot, wiped all 
connectbot 
data, and reinstalled connectbot.  It still goes directly to the text editor 
whenever I try use the "import keys" function.

Original comment by lauren4...@gmail.com on 29 Aug 2009 at 6:12

GoogleCodeExporter commented 8 years ago
If you're using the development versions, you can try r368 or older. I added 
support
for OpenIntents File Manager and AndExplorer for picking keys to import at that 
revision.

Original comment by kenny@the-b.org on 29 Aug 2009 at 10:55

GoogleCodeExporter commented 8 years ago
In the latest dev version, I commented out the OpenIntents and related code, 
and put 
back the simple file picker as a default and recompiled.  Problem solved for 
now, 
but something is clearly interacting badly with OpenIntents.  

Thanks.

Original comment by lauren4...@gmail.com on 29 Aug 2009 at 9:31

GoogleCodeExporter commented 8 years ago
Did your file have a .txt extension or something similar?

Original comment by kenny@the-b.org on 29 Aug 2009 at 10:53

GoogleCodeExporter commented 8 years ago
Negative.  Extension is "k1".

Original comment by lauren4...@gmail.com on 29 Aug 2009 at 11:06

GoogleCodeExporter commented 8 years ago
I'll do some more testing with those file managers. That is certainly naughty 
behavior.

Original comment by kenny@the-b.org on 2 Sep 2009 at 11:58

GoogleCodeExporter commented 8 years ago
I couldn't reproduce this with a couple different handsets. I'll just chalk it 
up to
strange file manager behavior.

Original comment by kenny@the-b.org on 17 Nov 2009 at 8:20