Import a key
Using the program — Import a key
Where: Keys → Import, Import key block / clipboard, or Bulk import (separate topic).
Use import when the key already exists (yours from another program, or someone else’s public key).
What you can import
- .asc, .pgp, .gpg files
- ASCII blocks:
text
-----BEGIN PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP PRIVATE KEY BLOCK-----
Public and secret may be in one paste; the store accepts what is valid. RSA 1024 is not imported for encrypt use; you are told it is obsolete.
Import from a file
- Keys → Import (or Import file).
- Choose the key file.
- Read the result: how many keys imported, or why a key was skipped.
- Find the new row; open Properties and check the fingerprint.
Import from a block or clipboard
- Copy the entire block, including BEGIN and END lines.
- Open Import key block (or Import from clipboard).
- Paste and import.
- “Zero key(s) imported” means the paste was incomplete, already in the store, or not OpenPGP key material.
Do not put a BEGIN PGP MESSAGE here. That is ciphertext; use File Task or Text Task.
What the program checks
- Duplicate fingerprint — already in the store; you are told it is a duplicate.
- Expired — imported or skipped per the message; do not encrypt to it.
- Revoked — same; row will be red if it is stored.
- Weak / 1024 — blocked for encryption use; you get a policy message.
- Malformed user ID — warning.
- Public only vs secret — Properties and the grid show whether private material is present.
After import
- Compare the fingerprint with the owner (Properties or QR).
- Set Verified only after that check. Import does not mean verified.
- If you imported your secret key, test decrypt of a file encrypted to it.
- Assign a group if you use groups.
If it fails
- Wrong file (a message file, not a key).
- Only the public half when you needed the secret.
- Key already in the store under a user ID you did not recognize (read the message; the “name” may be the user ID string).
- Idle lock closed the import window — paste again after sign-in.