Should I have multiple GPG keys?

Should I have multiple GPG keys?

In general, one key per identity should be fine. One key can include: Several UIDs (for separate mail addresses.) Several subkeys (for different devices, so you can put some subkey on your mobile; if it gets lost, revoke only this)

Are GPG keys secure?

Regardless of how you use GnuPG you should store the public key’s revocation certificate and a backup of your private key on write-protected media in a safe place. To help safeguard your key, GnuPG does not store your raw private key on disk. Instead it encrypts it using a symmetric encryption algorithm.

Can I use YubiKey with multiple accounts?

Can I use one YubiKey with multiple devices? Yes! Just plug your YubiKey into any computer and log in the way you normally would. That’s really it—you’ll be able to log in to all of your accounts, same as before.

How to get the correct order of UIDs in GPG?

If you want to get the correct order, you need to repeat these steps starting with the UID you want showing up second-to-last, all the way until the item you want displayed as the top (first) UID. The commands for doing this are (the text following $ and gpg> are what you type into the console):

How to make a UID appear at the top of the list?

You can make a UID appear at the top of the list by making it primary. The top UID then gets moved down to the second slot, and likewise, everything else shifts one space downward. It seems as though this “shift” only happens once you save the changes to the key.

Is it possible to rearrange the UID list?

The only guaranteed behavior is that the primary UID is listed first. Further rearranging them is not possible, and creates lots of clutter in the keyring, as each change requires new self-signatures.

Why do UIDs show up in the correct order?

Even if the UIDs show up in the “correct” order on your system, they do so because the order of database changes and the implementation of the database led to this, so a system seeing multiple changes at one time or using a different database backend is likely to behave differently.