Keyserver & Sharing
Publish and discover keys on OpenPGP keyservers.
What is a keyserver?
Section titled “What is a keyserver?”A keyserver is a database of public keys indexed by fingerprint, email, and key ID. Anyone can:
- Publish their key → others find it by email
- Search for someone’s key → download it
- Receive their key without sharing files directly
pgpilot supports two popular keyservers:
keys.openpgp.org (recommended)
Section titled “keys.openpgp.org (recommended)”- Privacy-respecting (does not list email addresses by default)
- Requires email verification (you control your own key listing)
- Modern, well-maintained
- Respects
--no-exportflag (your key can be private if you choose)
keyserver.ubuntu.com
Section titled “keyserver.ubuntu.com”- Traditional OpenPGP keyserver (Syncable pool)
- Lists all keys publicly (anyone can see your email)
- Large distributed network
- Better for finding keys by email
Publishing your key
Section titled “Publishing your key”Publish to keys.openpgp.org
Section titled “Publish to keys.openpgp.org”- In pgpilot, select your key in My Keys
- Click Publish
- A modal asks “Where to publish?”
- Choose keys.openpgp.org (default)
- Click Publish
- pgpilot calls
gpg --keyserver keys.openpgp.org --send-keys <fingerprint> - Status message: “Key published to keys.openpgp.org”
After publishing: keys.openpgp.org sends you an email verification link. Click it to activate your key listing.
Publish to keyserver.ubuntu.com
Section titled “Publish to keyserver.ubuntu.com”- Select your key
- Click Publish
- Choose keyserver.ubuntu.com
- Click Publish
- Status: “Key published to keyserver.ubuntu.com”
No verification email required; your key is immediately searchable (including email).
Checking publication status
Section titled “Checking publication status”pgpilot displays a Keyserver badge in the key detail panel:
- Unknown (gray badge) → status not yet checked
- Checking (spinner) → checking now…
- Published (green checkmark) → found on keyserver
- Not Published (red X) → not found
When you view a key’s details, pgpilot automatically checks keys.openpgp.org for your key’s presence.
Manual check
Section titled “Manual check”To re-check status:
- Select your key
- The badge updates automatically
- Or click Publish again to trigger a new publication
Auto-republish
Section titled “Auto-republish”Why? Keyservers expire old certificates. To keep your key fresh and discoverable:
pgpilot auto-republishes every 28 days:
- pgpilot remembers which keyserver you last used
- Every 28 days, it automatically re-publishes your key
- You’ll see a status message in the background
- This ensures subkey rotations and updates are always visible
You can also manually republish anytime by clicking Publish again.
Sharing your key
Section titled “Sharing your key”Once published, you have multiple ways to share your public key:
Via keys.openpgp.org search link
Section titled “Via keys.openpgp.org search link”https://keys.openpgp.org/search?q=alice@example.comAnyone can access this link and find your key by email.
Via paste.rs (temporary)
Section titled “Via paste.rs (temporary)”- Select your key
- Click Export → Paste
- A shareable link is generated:
https://paste.rs/abc123xyz - Share the link
This link works for 30 days (paste.rs default retention).
As an .asc file
Section titled “As an .asc file”- Select your key
- Click Export → File
- Save to
YourName.pub.asc - Share the file via email, upload to your website, etc.
Searching for someone’s key
Section titled “Searching for someone’s key”Use pgpilot’s Import view to find someone’s public key:
- Click Import in sidebar
- Select Keyserver
- Enter their:
- Email:
alice@example.com - Fingerprint:
ABCD1234567890ABCD1234567890ABCD1234567890 - Key ID:
1234567890ABCDEF
- Email:
- Choose keyserver (keys.openpgp.org or keyserver.ubuntu.com)
- Click Search
- pgpilot queries the keyserver and shows matching keys
- Click Import to add to your keyring
Best practices
Section titled “Best practices”-
Publish once, republish regularly
- Publish once to both major keyservers
- Let pgpilot auto-republish to keep current
-
Use email verification
- After publishing to keys.openpgp.org, check the verification email
- This prevents email hijacking/spoofing
-
Rotate old keys
- Old compromised keys should be revoked, not deleted
- Use Renew or Replace for subkeys
- Use
gpg --gen-revokefor master keys (not yet in pgpilot)
-
Verify before importing
- Always verify the key fingerprint before trusting
- Meet someone in person and compare fingerprints by hand
- Then set trust level in pgpilot (Marginal or Full)
Troubleshooting
Section titled “Troubleshooting”“Publication failed”
- Network issue — try again later
- Keyserver temporarily down — retry or use different server
“Key not published after 30 minutes”
- keys.openpgp.org may require email verification
- Check your email for a confirmation link from keys.openpgp.org
- Click the link and try re-publishing
“Found wrong key”
- If multiple keys exist for an email, pgpilot shows all
- Compare fingerprints carefully
- Only import keys you can verify
Next steps
Section titled “Next steps”- Learn about file signing & verification — see File Operations
- Manage trust — see Key Management (Trust Levels)
- Use hardware keys — see YubiKey / Smartcard