GpgOL: Populate key cache on startup
Closed, ResolvedPublic

Assigned To
Authored By
aheinecke
Oct 24 2018, 11:38 AM
Subscribers

Description

GpgOL should popluate the key cache on startup and only update it later. This would fix autoresolve failures e.g. if a mail composer was restored and we don't see the recipient change event.

But the main reason is that it would speed up the first verification as get_ultimate_keys would use cached keys and the signature status would already have a the key information.

Revisions and Commits

Related Objects