Implement an OSCrypt client for the Freedesktop Secret Service standard |
|||||
Issue descriptionhttps://specifications.freedesktop.org/secret-service/ The standard is an attempt to unify gnome-keyring and kwallet in a single API. Currently the Password Manager and OSCrypt components have separate implementations for each backends. Implementing an OSCrypt client for the standard will allow us to simplify the code, once the standard becomes widely adopted. Implementing one for Password Manager is unnecessary, due to issue 571003. As of this writing, gnome-keyring claims to have implemented the standard, while kwallet offers an experimental implementation.
,
Mar 4 2017
cfroussios@ -- thanks for filing this. Status "Available" with an owner assigned is slightly confusing, was it intentional, or did you mean "Assigned"? (Also I'm starring this issue now, so removing myself from Cc.)
,
Mar 6 2017
,
Mar 20 2017
,
Feb 10 2018
Right now the GNOME Key Ring in non GNOME desktops could asks for password each time Chromium is launched. When this happens is unpredictable. I have installed two systems with exactly the same set of software, and in one I get the error and in the other I don't. This is encouraging people to uninstall the Key Ring and store the secrets in plain text, which is a huge security risk: https://askubuntu.com/questions/31786/chrome-asks-for-password-to-unlock-keyring-on-startup https://forum.manjaro.org/t/skypeforlinux-weird-and-inconsistent-authentification-behaviour-gnome-keyring-bug/26076 I would reconsider the type and priority of this report.
,
Feb 12 2018
re #10 Implementing for Freedesktop Secret Service will not make the prompts go away, therefore the users will be just as motivated to uninstall Keyring. Once Keyring is uninstalled, it won't matter which API we will use to reach Keyring, because it just doesn't exist.
,
Feb 12 2018
,
Feb 12 2018
Issue 810991 has been merged into this issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by cfroussios@chromium.org
, Mar 3 2017