https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #30 from michaelk83 <mk.mat...@gmail.com> --- (In reply to nic.chris...@gmail.com from comment #29) > Unfortunately I'm already using pinentry-qt. Hmm.. that is unfortunate. > I see gpg has a "--pinentry-mode loopback" option, that redirects the > password prompt to the caller. Could this be used to have gpg request the > password from kwallet instead of calling back into org.freedesktop.secrets? > I guess it would require implementing the pinentry Assuan protocol into > kwallet If someone's going to implement the Assuan protocol, they may as well make a new pinentry tool that *doesn't* try to access KWallet (or Secret Service) while it's unlocking. But the loopback method is similar to my suggestion to have KWallet prompt for the passphrase before trying to unlock GPG. If you're willing to mess with this some more, I'd like to confirm which process is making the `OpenSession` call - is it indeed pinentry-qt, or not? Rather than trying to do this at login, you can close KWallet and clear the key from gpg-agent before launching whatever tries to read secrets. But I'm not sure how to translate the DBus sender ID to the process ID... I've found these two suggestions, not sure how useful: https://stackoverflow.com/a/69318327/15047974 https://unix.stackexchange.com/a/498093/455274 For clearing gpg-agent: https://askubuntu.com/questions/349238/how-can-i-clear-my-cached-gpg-password -- You are receiving this mail because: You are watching all bug changes.
