https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #69 from michaelk83 <mk.mat...@gmail.com> --- > as long as pinentry makes the request via the Secret Service API, KWallet has > no way to know that it's its own password that is being requested here. On 2nd thought, if pinentry always uses the same lookup attributes, KWallet could potentially detect those, and return an error or empty response, indicating that the wallet password is not cached. That may force pinentry to ask the user, as intended. But the attributes may vary somewhat depending on the wallet, GPG key, user, etc. -- You are receiving this mail because: You are watching all bug changes.
