https://bugs.kde.org/show_bug.cgi?id=515024
michaelk83 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Add support for different |Migrate plasma-nm to |secrets backends with |QtKeyChain |QtKeyChain | CC| |[email protected] See Also| |https://bugs.kde.org/show_b | |ug.cgi?id=504312 --- Comment #2 from michaelk83 <[email protected]> --- Plasma-nm not directly supporting Secret Service (via QtKeyChain) is really the main issue in bug 504312. But 504312 focuses more on the connection problems than the migration to QtKeyChain, so I'll leave this one to focus on the migration. A few notes on your analysis: - I wouldn't recommend sharing the Secret Service DB between machines. It's designed for local use, and most client apps don't include a machine identifier in their secret keys. So there's not much use including it in the plasma-nm keys. - If plasma-nm needs to store a JSON map, it can just store the JSON string as the secret value. There's no need to change that part. - It can't use "psk" as a part of the key, since that's a selectable option that's directly related to the password. It tells plasma-nm how that password is used. So it needs to be part of the value (or a separate value in a related key). - There's no need for a manifest. Plasma-nm knows exactly which keys it needs for each connection. - The QtKeyChain API is already quite simple. It doesn't need an extra wrapper layer. - There's no need to migrate data. This is taken care of by KWallet. If you're using KWallet as the Secret Service provider, it already has the data internally, and exposes it through the Secret Service API using the QtKeyChain schema (and also via the old KWallet API). If you're using it as a proxy to a different provider, then it would have already migrated the data to there (with the same schema). You just need to make sure you're reading (and writing) the correct keys. - The fallback from Secret Service to KWallet API is handled automatically by QtKeyChain. You don't need to mess with that. -- You are receiving this mail because: You are watching all bug changes.
