Summary | Add support to fetch GPG keys by fingerprint/id |
Queue | IMP |
Queue Version | Git master |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | enrico.scholz (at) informatik (dot) tu-chemnitz (dot) de |
Created | 12/30/2004 (7505 days ago) |
Due | |
Updated | 11/13/2013 (4265 days ago) |
Assigned | 12/31/2004 (7504 days ago) |
Resolved | 11/13/2013 (4265 days ago) |
Milestone | IMP 5.0 |
Patch | No |
State ⇒ Rejected
Version ⇒ Git master
store local copy of key if it exists on a keyserver.
State ⇒ Stalled
keyservers when editting a contact or something else?
with the abstract and dynamic nature of Turba.
keyservers when editting a contact or something else?
State ⇒ Assigned
Your second request is bogus. There is absolutely nothing (e.g. RFCs)
that says that a PGP program MUST use a keyserver to download/get
keys. Therefore, if we are going to store any keys locally, it must
be the full key text.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ RFE: add support to fetch GPG keys by fingerprint/id
Queue ⇒ IMP
State ⇒ New
only (it works already when verifying signatures). Currently, the key
has to be extracted manually and entered completely.
It would be nice also, when not the GPG key itself but only the
identifying fingerprint would be stored in the database.