https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #7 from michaelk83 <mk.mat...@gmail.com> --- (In reply to Michi from comment #6) The main goal of this task, as I understand, is to have KDE apps access passwords from the pass backend. The proposed solution was to integrate pass with KWallet, and then have the apps access KWallet. What I'm saying is that KDE apps can already access the pass backend via the Secret Service API, via e.g. https://github.com/mdellweg/pass_secret_service . They don't need KWallet as a middleman. *Alternatively*, you can store all your passwords in any one of the other Secret Service backends, *without pass*, and have the apps access them there. KWallet can now also act as such a backend, as of 5.97.0. (It may eventually drop the old API, leaving only Secret Service - Bug 458318). IOW, the apps would access all their passwords through Secret Service either way. You have a choice between different backends where to store the passwords: pass + pass_secret_service, KWallet, Gnome keyring, KeePassXC, etc. I don't see a reason to mix different backends. -- You are receiving this mail because: You are watching all bug changes.
