https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #9 from michaelk83 <mk.mat...@gmail.com> --- (In reply to Borden from comment #8) At least at the moment, KWallet and pass are two completely separate systems. They can each present the same Secret Service API to client apps, so the apps don't care which one is being used. (Pass needs some help for this from pass_secret_service or similar; KWallet needs at least version 5.97.0). Pass has its own collection of front-ends. KWallet is not needed for this at all. "KWallet" is actually two parts: KWallet daemon (aka KWallet Frameworks) is the backend, and KWalletManager is the front-end. KWalletManager can only talk to KWallet daemon. But with the new Secret Service support, you can replace KWalletManager with some other front-end such as Seahorse. (Technically, it was also possible with the old KWallet API, but I'm not aware of any other GUI front-ends to that API besides KWalletManager). Regardless, KWallet (both parts of it) has been suffering from lack of developers for at least half a decade. AFAIK, it's an old, neglected piece of software, full of all sorts of problems. I expect that once the migration to Secret Service is more mature, KWallet will eventually be discontinued. KeePassXC is a popular alternative, but once again, it's not a front-end. KeePassXC is a complete package of its own, backend + front-end in one. But it is cross-platform, has many good features, and can present the same Secret Service API to client applications. The direction for Linux is to have all client apps talk to Secret Service. Then you can switch in whatever backend you want for that, and write as many different front-ends as you want. They would all talk through the same API. But Secret Service itself is based on DBus, which is mostly Linux-only. If you want something really cross-platform, my recommendation goes back to the KeePass ecosystem. -- You are receiving this mail because: You are watching all bug changes.
