https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #70 from michaelk83 <mk.mat...@gmail.com> --- > if pinentry always uses the same lookup attributes, KWallet could potentially > detect those I forgot that the deadlock is in the `OpenSession()` call, so this is not possible. I think that handling the Assuan protocol in KWallet is the only proper fix here. But if KWallet will eventually be sunsetted as suggested in https://invent.kde.org/frameworks/kwallet/-/merge_requests/97 , then messing with the Assuan protocol may not be worth the effort. In that case, I would recommend to close this as a wontfix, and instruct users to use the available workarounds, as listed here in comment 36, and explained further in comment 39 and comment 46. Regarding the concern that was raised by Thiago Macieira: > I disagree that no-allow-external-cache is a proper solution. It's a > workaround, but > it prevents one from using GPG/pinentry for other tasks and saving the > credential > cache in the KWallet-provided Secret Service. If you absolutely have to have the external cache enabled for GPG, then you have two other options: either use a blowfish wallet, or use a different Secret Service provider, which doesn't rely on GPG storage. But keep in mind that gpg-agent has its own internal cache, even when the external cache is disabled. It would simply not cache persistently across login sessions. For most users, setting `no-allow-external-cache` in `gpg-agent.conf` is the correct workaround. -- You are receiving this mail because: You are watching all bug changes.
