Export of keys and keyrings is not available

[Rūdolfs Mazurs]

Binary package hint: seahorse

When I try to export key or keyring, the menu is grayed out. Thus I cannot make backups of my keys.

That would be only a inconvenience, if I could just backup keys by copying seahorse configuration directory. I guess I can do that, if only I knew, where it actually is. It is certainly NOT .gnupg, because when I delete it (in recovery mode, as root), the keys are still there and .gnupg folder is as good as new.

It would be very nice to do something about this. When I made a keyring and put all my brand new passwords there, the seahorse somehow managed to lose all keys in it.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: seahorse 2.29.91-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
Architecture: i386
Date: Sun Mar 28 11:06:43 2010
ExecutablePath: /usr/bin/seahorse
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091203)
ProcEnviron:
 LANG=lv_LV.utf8
 SHELL=/bin/bash
SourcePackage: seahorse

[Aiden83 (aidendeem)]

You might be able to backup your keys with the command:
gpg --export

or

gpg --export-secret-key

From man gpg:
"--export Either export all keys from all keyrings (default keyrings and
              those registered via option --keyring), or if at least one name
              is given, those of the given name. The new keyring is written to
              STDOUT or to the file given with option --output. Use together
              with --armor to mail those keys."

[Cristóbal M. Palmer (cristobalpalmer)]

You can make a backup by copying ~/.gnome2/keyrings to a secure location. This is still a problem, however, because after a reinstall and pulling in my login.keyring from a backup I am in the position of having two keyrings, both of which have data which I would like to be 'default' in some sense. Without a robust export option, how can I merge these two keyrings?

[davti (tim-g-davenport)]

I'm seeing the same issue and cannot edit passwords either.

[Cypher1101 (cypher1101)]

I cannot edit keys or export keyrings either

[elmimmo (chocolate-camera)]

I cannot export passwords or move passwords from folder to folder either. Using Ubuntu Linux 10.04 Lucid Lynx

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version. Thanks in advance and sorry for the late response.

[Evan Derickson (derickson-e)]

I'm getting an unavailable export option in Natty.

[Oded Arbel (oded-geek)]

This is still the case with seahorse in Ubuntu 11.10

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Kirils Solovjovs (linux-kirils)]

same for 12.04

[Evan Derickson (derickson-e)]

This appears to be fixed in Seahorse 3.8.2, Ubuntu 13.10

[Sebastien Bacher (seb128)]

Could you describe what you try to do exactly? Using the current version, the export menu is available if you select a gpg key

[Ihor Kaharlichenko (madkinder)]

Sebastien, the point is that you cannot export a password keyring and then import it elsewhere. At least as of Seahorse 3.2.2 shipped in Ubuntu 12.04.

[George Fragos (anvo)]

Any solution to this malfanction of Seahorse v.3.2.2 in Ubuntu 12.04...?

[maik stolle (ms090780)]

same problem on 14.04 seahorse 3.10.2
"export" is grayed out!

regards maik

[Jorge Morais (jorgemorais)]

I am affected by the problem on 14.04. The "export" menu entry seems available for my OpenSSH key, but it is greyed out when I select a password keyring. I want to export my passwords to Keepass2, so I could synchronize with my Android smartphone.

Should this bug be filed upstream? In that case, would it be better to wait for the Ubuntu Seahorse mantainer to file it, or should I file it myself?
Regards

[Daniel Richard G. (skunk)]

Jorge: Check in the upstream bugzilla to see if someone's already filed a bug, but if not, then go for it. Very few Ubuntu package maintainers take the initiative to file upstream bugs themselves.

If you do file a bug upstream, or a report already exists, please link it here!

(As a possible workaround: I've found in the past that if a password keyring is set to have no passphrase, the on-disk file becomes cleartext. Keepass2 should certainly be able to import that.)

[cogset (jackfog66)]

This issue is still present in Ubuntu 15.10: Seahorse to date still has no option to export/import stored passwords.

This kinda hinders its abilities as a password manager: even if it's probably meant to be mainly a gpg key management interface, it also has this ability to store passwords, so not being able to export/import those as well detracts from its usability forcing users to seek alternative solutions.

Given that there has been no activity in this bug since 2014 (see comment above), should eventually a new bug be opened tagging current and future releases?