I had a similar problem when the public key spaned multiple lines
(however, using it with ssh worked).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/372608
Title:
import
This is reported fixed in the upstream bug tracker, but currently
seahorse 3.4 has not landed in 12.04, I know some Gnome 3.4 applications
are making it into the LTS but it's not clear if this will happen for
seahorse before release, if anyone has more info on the status of that
it might help
I can confirm that I was successfully able to import an ssh key using
seahorse, I got a segfault as documented in this bug:-
https://bugzilla.redhat.com/show_bug.cgi?id=751515
But my key was imported successfully on 12.04.
So... half way there... now we just need to do it without crashing. ;)
To get seahorse to automatically add the key, you will have to export
the public key and save it as id_rsa.pub.
$ ssh-keygen -y
Enter file in which the key is (/home/pravin/.ssh/id_rsa):
Enter passphrase:
And then save the public key generated in a file called id_rsa.pub
(using copy+paste)
--
** Changed in: seahorse (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/372608
Title:
import failure: Invalid file format
--
desktop-bugs
I had a similar issue - but I would never get any error message
displayed, seahorse would just exit with no message, leaving behind a
partial copy of the key missing a few bytes from the end at
~/.ssh/id_rsa (or ~/.ssh/id_rsa.1 if that already existed). If I ran
from console I would see the same
I *was* having the same problem here in Jaunty. This should be a bug,
and should be fixed. It was not a mime-type issue for me (though I saw
the same /symptoms/ as others report).
Copying the public key line out of authorized_keys2 and creating
id_dsa.pub, then running seahorse, there was not
Same problem, this time with a pgp key. Running karmic. An identical
import worked fine on hardy.
--
import failure: Invalid file format
https://bugs.launchpad.net/bugs/372608
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in
Forgot to add, the workaround I used was to rename my (private) pgp keys
as foo.pgp, then I was able to import them just fine.
--
import failure: Invalid file format
https://bugs.launchpad.net/bugs/372608
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
i figured out, the name of the files doesn't matter as long as both
files have the same name (public key with .pub) and are in the same
directory (~/.ssh/).
but the import functionality should be fixed.
--
import failure: Invalid file format
https://bugs.launchpad.net/bugs/372608
You received
I can confirm that on karmic 64bit with all latest updates applied I
cannot manually import ANY keys, rsa, dsa, encrypted or not as it always
complains about Invalid file format. Makes the application kinda
useless for any keys other than ~/.ssh/id_rsa...
--
import failure: Invalid file format
In bug 397145 it was pointed out that importing your ssh keys happens
automatically if ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub are both present.
Did you maybe rename your public key file? That was what make the SSH
agent stuff not work on my system. I haven't tested, but I suspect that
key importing
Is seahorse simply linked against the wrong library in Ubuntu?
I tried filing https://bugzilla.gnome.org/show_bug.cgi?id=597310
with this info
and...@salt2:~/devel/gtktest$ cat test.c
#include gtk/gtk.h
#include gio/gio.h
#include glib/gstdio.h
int main( int argc, char *argv[] ){
Experience the same behavior under Karmic beta.
--
import failure: Invalid file format
https://bugs.launchpad.net/bugs/372608
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
desktop-bugs mailing list
The mime-type checking that Seahorse uses does seem broken to me.
http://git.gnome.org/cgit/seahorse/tree/libseahorse/seahorse-util.c#n793
which i think calls
http://git.gnome.org/cgit/glib/tree/gio/gcontenttype.c#n319
which has no chance of returning eg. application/x-ssh-key
--
import
Thank you for the hint, but this is unrelated I believe - both my keys
are identified as application/octet-stream by xdg-mime.
But I just discovered that it seems to be related to DSA keys in
seahorse in general. I was not able to generate a DSA key with ssh-
keygen or puttygen which would be
I get the same problem as comment #4 but using RSA keys.
Version 2.26.1 on Jaunty,
--
import failure: Invalid file format
https://bugs.launchpad.net/bugs/372608
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
This may be related to bug 397145 which I just filed. Basically I
suspect that seahorse and gnome-keyring-manager refuse to recognize the
id_rsa file because it isn't recognized as the proper mime type. Can you
check your key file to see what mime type it is identified as?
Also, can someone who
I can confirm that it does not work in jaunty (dont know about earlier
versions).
I have two private ssh keys in my .ssh directory:
- one RSA-key generated with ssh-keygen - it gets picked up automatically as
expected by seahorse
- one DSA-key generated with putty, and exported through putty to
I can confirm that it does not work in jaunty (dont know about earlier
versions).
I have two private ssh keys in my .ssh directory:
- one RSA-key generated with ssh-keygen - it gets picked up automatically as
expected by seahorse
- one DSA-key generated with putty, and exported through putty to
20 matches
Mail list logo
