https://bugs.kde.org/show_bug.cgi?id=399232
--- Comment #8 from B Rhodes <i...@bordenrhodes.com> --- I'm 110% in support of having KWallet be a front-end to a 'proper' OS password management service. Of the lot, I think Pass is the best candidate because of its near universal portability across *nix systems, its adherence to Unix philosophy, and brilliantly simple design. However, as one of KDE's objectives is to be cross-platform, what considerations are there to hooking into other OS backends? Or is the intention for KWallet to be a *nix -only system? For example, Mac OS stores passwords in Keychain. Although Mac ought to support Pass, Keychain might be a better backend for KWallet (although there's a good argument for segregating passwords from the Apple ecosystem). Likewise, Windows doesn't have a proper password manager, and my experience in using Pass on Windows is that it's very slow and cumbersome because it seems that GPG struggles with Windows. Regardless, .kwallet files are too esoteric for a portable operating system, so turning KWallet into a front-end makes a lot more sense (and should save the devs some time if a proper API call can be developed). -- You are receiving this mail because: You are watching all bug changes.
