Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

20
  • 5
    Is the exported key (second command) encrypted or do I need to encrypt it by myself before storing it on a.g. a USB drive? Commented Feb 18, 2019 at 10:53
  • 3
    @Julian ... The exported secret key has the same protection as the secret key that was exported. If there was a passphrase, the passphrase is required to import the secret key. Commented Feb 18, 2019 at 12:55
  • 4
    @OMGtechy How did you try to recover the key(s)? I could restore public keys by gpg --import-options restore --import backupkeys.pgp, but that does not restore secret keys, only the public ones, if backupkeys.pgp was created by gpg --output backupkeys.pgp --armor --export --export-options export-backup. In that --armor is not necessary and export-backup could be replaced by backup. Commented Dec 15, 2019 at 0:52
  • 2
    Note that Keybase has since been bought by Zoom, who have very close ties to China. Commented Jul 4, 2020 at 19:12
  • 2
    It may be convenient to export based on the keypair fingerprint if the same email address has been used for multiple keypairs, e.g. gpg --armor --export <fingerprint> > <fingerprint>.public.asc - you can also use the long keyid which is the last 16 chars of the fingerpint. cc @user643011 Commented Dec 5, 2024 at 15:26