Chromium v53 (v11 cookies and libsecret backend on Ubuntu)

[oltodosel]

The latest version of chromium has new cookies that start with 'v11' and wouldn't decrypt.

[n8henrie]

Please provide your operating system and version info.

[oltodosel]

Linux 4.7.2-1 x86_64
Chromium 52.0.2743.85-20 - has encrypted cookies with v10 at the beginning and it works fine.
Chromium 53.0.2785.92-1 - has encrypted cookies with v11 at the beginning and decryption doesn't work.

[n8henrie]

Looks like linux still uses the same implementation (v10 / saltysalt / peanuts) unless you're using a third party password-based system.

Still the old version:

• https://chromium.googlesource.com/chromium/src/+/53.0.2785.100/components/os_crypt/os_crypt_posix.cc
• https://chromium.googlesource.com/chromium/src/+/53.0.2785.100/components/os_crypt/os_crypt_mac.mm

Comments on new version with option for v11:

• https://chromium.googlesource.com/chromium/src/+/53.0.2785.100/components/os_crypt/os_crypt_linux.cc#35

I don't know much about libsecret, I'll have to see if I can figure out how to retrieve the new password for these systems.

[djtm]

I've noticed that for some values, the encrypted key does not start with either v10 or v11. Examples include __ar_v4 from .hub.docker.com/, ref from www.intel.com/. But it's still encrypted in some way...

[n8henrie]

@djtm Hmm, I am only seeing v10 for Docker.com currently. Do you think this is related to this issue?

[djtm]

I'm not 100% certain it's the same issue. I'll do more testing in the future, next week if all goes well. :)

[stuglaser]

I am also seeing cookies with a v11 prefix.

Here is an example (from running select * ... in sqlite): v11�I�̫P3ζ�VnG@��[u�}�Ҵ����X-�vfw�kOt"p|��uw6;

Here is the same example base64 encoded: djEx+EmEzKtQM862HVZuR0C3+1t1r33b0rSv6KAWWC0UdmZ3o2tPPwh0InB87dR1dzY7

I am running Google chrome 54.0.2840.71 on Linux (ubuntu)

[n8henrie]

Huh, still working for me on OS X, all v10 cookies, and my Linux box broke. Reinstalling Arch, will be able to test soon. Would appreciate help from anyone knowledgeable about libsecret as mentioned above -- hopefully it may be as simple as getting the Chrome pw from keychain on OSX.

[djtm]

I think starting Chrome with --password-store=basic might be a workaround.

[djtm]

It looks like it's implemented here: https://github.com/bertrandom/chrome-cookies-secure/blob/master/index.js

I'm guessing /usr/bin/google-chrome --use-mock-keychain might also be the right way to avoid the issue.

Affecting me too.. I've been trying to get the passwords out of keyring with no luck. --password-store=basic and --use-mock-keychain didn't work for me

These might be interesting:
https://chromium.googlesource.com/chromium/src/+/53.0.2785.100/components/os_crypt/key_storage_libsecret.cc
https://developer.gnome.org/libsecret/unstable/py-lookup-example.html

Okay so I managed to extract the passwords from libsecret, they are in a service called "Chrome Safe Storage"

import gi
gi.require_version('Secret', '1')
from gi.repository import Secret

def get_cookie_password():
    service = Secret.Service.get_sync(Secret.ServiceFlags.LOAD_COLLECTIONS)

    default_keyring = service.get_collections()[0]
    default_keyring = service.unlock_sync([default_keyring])[1][0]

    for item in (default_keyring.get_items()):
        if item.get_label() == "Chrome Safe Storage":
            item.load_secret_sync()
            return item.get_secret().get_text()

    return None

Hit me up if that doesn't work for you

You can also use the command line:

$ secret-tool search application chrome