Ubuntu Chromium Snap prevents encrypted storage of passwords by default(bugs.launchpad.net)
bugs.launchpad.net
Ubuntu Chromium Snap prevents encrypted storage of passwords by default
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267
3 comments
Ubuntu ships a Chromium browser that has its abilitiy to store passwords safely sandboxed/containerized away.
I did not expect that, given that Ubuntu comes with a full GUI and thus safe password storage backend available in theory.
Because this issue is open since 2022, I wrote a repro that proves its existence:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+...
All credit goes to user "Erlenmayr" who reported this.
I did not expect that, given that Ubuntu comes with a full GUI and thus safe password storage backend available in theory.
Because this issue is open since 2022, I wrote a repro that proves its existence:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+...
All credit goes to user "Erlenmayr" who reported this.
To see whether there are plain text passwords on your non-Snap chromium, change this line in the linked password dumper script:
- db_path = os.path.expanduser("~/snap/chromium/common/chromium/Default/Login Data")
+ db_path = os.path.expanduser("~/.config/chromium/Default/Login Data")
I understand that Google wants users to always be logged into their Google account, so they have to make the built-in option worse than the cloud option, but that's no excuse for purposely making the built-in option insecure. If you're not going to make a secure password manage an option, don't include one at all.
I don't want my passwords stored on the cloud, for obvious reasons, and I'm not a fan of Linux keyrings relying on D-Bus for security, and considering that there's only one application that I would store passwords for, I might as well have them stored by that application, if it can do so securely.