Hi, oo7 author here > Will seahorse use this backend also, or will it still use GNOME keyring daemon?
Seahorse uses the secret service API underhood, so it should work with both oo7-daemon and gnome-keyring-daemon. No need for the later anymore. Will the secret-tool CLI and libsecret use this backend by default? Yes. But we have a better replacement of secret-tool called oo7-cli. For example the former doesn't prompt you to unlock a keyring when using the CLI, oo7-cli does. It also supports reading local keyrings (your backups, if you pass in the secret to decrypt them). Note I do have a goal to replace the libsecret API with something else but no work is being done there. > Will this work seamlessly with the existing git-credential-helper? No clue what is that, but it likely uses secret service dbus api, so it would work. Test it? :) > Will existing askpass utilities that currently work in gnome for gpg and ssh still work with this? Those are not related. > GNOME supports multiple keyrings. Will this support multiple keyrings? On upgrade, how will secrets be migrated if multiple keyrings are used? Will migration be easy if the GNOME keyrings are not unlocked by PAM (because they have a different passphrase than the account, for example). The new daemon supports multiple keyrings, auto unlock through PAM and if the password is not provided through PAM, then the user is prompted to unlock them the moment you interact with them. How, if at all, will saved passwords in GNOME Online Accounts (goa) be affected? same as above, that uses secret service dbus API, it just works. Will any fedora-packager tools be affected, such as fpkinit? No clue what that uses. -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
