https://bugs.kde.org/show_bug.cgi?id=459039

michaelk83 <mk.mat...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mk.mat...@gmail.com
           See Also|                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=458318

--- Comment #2 from michaelk83 <mk.mat...@gmail.com> ---
AFAIK, KWallet has suffered from a shortage of developer time for many years.
It is indeed outdated, and not likely to be vastly improved any time soon.

The overall direction for Linux is to switch to Sercret Service, and kwalletd5
has very recently received its own Secret Service API support. This now creates
a common interface between the different secret storage backends, client
applications, and manager applicatons, so different backends become
interchangeable, and different managers become interchangeable. Instead of a
manager specific to kwalletd5, you would have a manager for Sercet Service, and
it would be able to talk to any of the Sercret Service backends.

Right now, there is Gnome's Seahorse, which can now talk to kwalletd5 as well.
There's no KDE-native equivalent yet, that I'm aware of. But there is now both
the ability and justification to develop one. (There is also KeePassXC's own
UI, but that can only talk to KeePassXC.)

As the migration to Secret Service matures, eventually, the old KWallet API can
be deprecated (Bug 458318), and at that point, either KWalletManager will need
to be ported to Secret Service as well, or it will need to be replaced by a new
Secret Service manager.

I agree that an official KDE fork of KeePassXC is also an interesting idea. In
the mean time, if you encounter a KDE app that doesn't support Secret Service
yet, encourage its maintainers to switch to QtKeyChain, or at least to
libsecert. The former is preferred. It supports both Secret Service and the old
KWallet API.

As for your concerns with KeePassXC, you can try raising those with KeePassXC's
developers (but do search for existing issues first).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to