Issue metadata
Sign in to add a comment
|
Fedora 25: Chrome 56 stores passwords internally, not in gnome-keyring
Reported by
nateggra...@gmail.com,
Jan 30 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 Steps to reproduce the problem: 1. Install Fedora 25 with GNOME 3.22 2. Upgrade to Chrome 56 from Chrome 55 3. Navigate to a website that requires login credentials 4. Log in and tell Chrome to save the password when prompted 5. Open gnome-keyring and search for the password What is the expected behavior? The password should be saved in gnome-keyring, like it was in Chrome 55 and all prior versions of Chrome. What went wrong? Instead, the password is saved in Chrome's internal password manager. Same thing happens when trying to read passwords: passwords saved in gnome-keyring are not recognized. Did this work before? Yes Chrome 55 Chrome version: 56.0.2924.76 Channel: stable OS Version: Fedora 25, GNOME 3.22 Flash Version: Shockwave Flash 24.0 r0 Chromium 55 is still able to read from and write to gnome-keyring, so it doesn't appear to be an issue with gnome-keyring, GNOME, or GTK.
,
Jan 30 2017
engedy, do you know if there were any changes recently with how passwords are stored on Linux?
,
Jan 30 2017
Is this related to changes in https://bugs.chromium.org/p/chromium/issues/detail?id=602624 ?
,
Jan 30 2017
Adding Christos who worked on this.
,
Jan 31 2017
It sounds like either Chrome stopped expecting to find gnome-keyring in this linux distribution, or it fails to load the keyring libraries. Let's examine the easy part first. If you run Chrome with --password-store=gnome, does still ignore keyring? Also, what's the state of the gnome-keyring in question? Does it auto-unlock, or is it unlock manually via a prompt? If it is manual, do you still get prompt(s) after the update?
,
Feb 1 2017
...And just like that, after rebooting into a Wayland session to test, I can no longer reproduce the issue. The only system change I made since reporting the issue was fixing https://bugzilla.redhat.com/show_bug.cgi?id=1417431. Could that have caused it?
,
Feb 2 2017
,
Feb 2 2017
Did anybody manage to reproduce this issue locally?
,
Feb 3 2017
,
Feb 3 2017
,
Feb 3 2017
Removing myself, because cfroussios@ is the best person to talk to about this. Happy to get re-involved on demand, though.
,
Feb 7 2017
cfroussios@, could you help triage this bug? If nobody can repro it anymore, please feel free to mark it won't fix. Thanks!
,
Feb 7 2017
I didn't repro. Since there is only one report of this and it fixed itself, we can't investigate further.
,
May 17 2017
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nateggra...@gmail.com
, Jan 30 2017