Seems like KDE Wallet is perfectly sufficient, so in which circumstances may someone wish to prefer the freedesktop.org secret service?
That’s what KeePassXC uses when KDE Wallet is disabled: KeepassXC and secret service, a small walk-through. · Alejandro's Blog
don’t gnome keyring and kwallet use the secret service too? it makes it possible to use either, including keepassXC, to manage your passwords natively.
see this:
https://specifications.freedesktop.org/secret-service/latest/ch01.html
This API was designed by GNOME and KDE developers with the goal of having a common way to store secrets. Its predecessors are the desktop-specific APIs used by GNOME Keyring and KWallet.
Interesting. So it’s somewhat better to use the secret service through KeePassXC? Newer, better code?
Interesting. So it’s somewhat better to use the secret service through KeePassXC? Newer, better code?
Well, it’s not like kwallet is unmaintained. It’s a core Plasma component.
I’ve tried to use the keepassxc’s secret service integration, but found it lackluster compared to kwallet, which works nicely for native password saving and autofill. It didn’t start when needed, although i should note that i use the flatpak version.
I use kwallet to store my hard drive encryption passwords and to store mastodon session tokens for tokodon, which afaik cannot store them anywhere else. Kwallet unlocks on login, so that the passwords are autofilled without any interaction.
I cannot figure out why would anyone use secret service integration for personal passwords which have nothing to do with the operating system as in my case.