Failure to detect some existing SSH keys

Bug #520052 reported by Paul Natsuo Kishimoto on 2010-02-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ground Control

Bug Description

Related to question #100399. Ground Control preferences prompts me to create new keys, and commit/push operations usually fail.

Local public key:

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAtRvMlv3E1xJO8WLE4IGzlWLdWESaNOuOgAVDA18J8+57sXjnG6B9NFEacf574Gg/nxF2vTV1K7bJ9PpTKgiUG/kofIygiK9JxfYn9ThLS9Ac/jPqiiZAMXSwGzDZjupLfkJc8r/wNmya3YZWQlCyD4jls4d+fWNM3y3UgTLMIJ9XYoO9UAfmefwkzJSoPCfgz6T/l9lmWHGOfi8xsRjGhNuFtHtcTFn1V2SYjjoG8IOrSWLt7Zjr6n9KjZr1guahEJnizLG826Vr2UI0O+jmUkEAfuotA09hUHCxOC6StNxIalFzRHw75QT/m1TmVfYsftMMuK+2PUOF3tTI9oxifQ== <email address hidden> -- khaeru-desktop

Launchpad public key:

Key type

Key text

    <email address hidden> -- khaeru-desktop

One wrinkle is that the local *private* key is a symlink to an ecryptfs volume set up in the usual way (

.ssh/id_rsa -> /home/username/Private/.ssh/id_rsa

...but the target file has correct permissions. SSH and Nautilus work fine in this configuration. is *not* symlinked.

Martin Owens (doctormo) wrote :

I'm changing the title because groundcontrol doesn't fail to use existing ssh keys. It just mishandles detection on some keys for checking up on keys installed.

But that's very much for including the keys in the bug report, will help a lot.

Changed in groundcontrol:
importance: Undecided → High
status: New → Confirmed
summary: - GC fails to use existing SSH keys
+ GC fails to detect some existing SSH keys
summary: - GC fails to detect some existing SSH keys
+ Failure to detect some existing SSH keys
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions