https://bugs.kde.org/show_bug.cgi?id=522998
michaelk83 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from michaelk83 <[email protected]> --- AFAIK, KeepSecret only talks to the Secret Service API, which has no notion of a "wallet password". The "wallet" terminology is left over from KDE KWallet, however, the actual storage backend for KeepSecret may also be GNOME Keyring, KeePassXC, pass, etc. The correct terminology in Secret Service is "collection", rather than "wallet". Anyway, each of those (and other) backends have their own notion of how to manage the collection passwords, and some may not even have collection passwords. The Secret Service API spec lets each service choose the lock granularity: > It's up to the service whether to unlock items individually, or collections > as a whole. > The client application should act as if it must unlock each item individually. https://specifications.freedesktop.org/secret-service/latest/unlocking.html So there isn't much that can be done here, IMO. Your best bet is to create a new collection/wallet, and migrate the passwords there. At best, KeepSecret might be able to automate that. For now, there's a new export/import feature that was finished a few weeks ago. It should be out with the next version, I suppose. -- You are receiving this mail because: You are watching all bug changes.
