Chromium is not using Gnome Keyring; passwords are stored in plaintext

ThePacman · 2014-01-20 21:37:26

I'm running Chromium 32.0.1700.77 with Gnome Keyring 3.10.1.
I'm using LightDM.

The relevant section of my ~/.xprofile is

# Start a D-Bus session
source /etc/X11/xinit/xinitrc.d/30-dbus
# Start GNOME keyring
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK

(~/.xinitrc just sources my xprofile and starts the DE)

/etc/chromium/default sets the flags for Pepper Flash, the PDF reader, and the entry I added: "--password-store=gnome".

Seahorse reveals that I have two keyrings, Login and Default. Login contains one entry, "Unlock password for: Default", which contains the password for Default (which contains all of my Chromium passwords.) Login gets unlocked automatically if I log in via DM (its password is the same as my user password.)

All is well and good, until I begin via startx on a TTY (after rebooting to ensure all gnome keyring daemons are stopped), at which point all passwords are accessible without any authentication. If I stop the browser and remove ~/.config/chromium/Default/Login\ Data, then the passwords don't appear immediately in chrome://settings/passwords, but get immediately repopulated by sync - how did the browser log into sync if all the sensitive data was supposedly stored in the keyring?

I have already tried wiping ~/.config/chromium/ and deleting the Default keyring (incase an initial run of the browser had been run without --password-store=gnome and stored away plaintext authentication,) but that wasn't the case.

Tl;dr: my Chromium passwords and sync authentication details are accessible without the gnome keyring.

Last edited by ThePacman (2014-01-20 21:38:50)

Arch Linux

#1 2014-01-20 21:37:26

Chromium is not using Gnome Keyring; passwords are stored in plaintext

Board footer