To avoid additional keylistings esp. when users insist on always showing the key approval dialog we might want to consider moving the dialogs into Kleopatra so that kleopatra can be autostartet and then just bring up the dialogs without having to do additional keylistings.
Description
Related Objects
- Mentioned Here
- T7308: Speed up the X.509 key listings
Event Timeline
Either this has super high priority or we fix S/MIME keylistings in GnuPG. I will write a mail with details as that involves customer information.
Something which has high priority but has not been touch can't have a super high priority.
The problem is that this is a just a band aid at best. The underlying problem that shows up in other places is not fixed. We should apply the band aid only if we say we don't fix the underlying problem.
Alright, we should do that in any case because two key caches are never a good idea and in particualr not if one of them needs too be reloaded too often. Thus re-using the one in Kleopatra is the proper solution. I recall that we looked at this at a time when we already started to design gpgol2 which would solve the problem anyway. However, at least for vsd we need to keep on using the classic gpgol for quite some more time. Thus the effort to improve the key resolving in gpgol is really justified.