-
-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chromium v53 (v11 cookies and libsecret backend on Ubuntu) #12
Comments
Please provide your operating system and version info. |
Linux 4.7.2-1 x86_64 |
Looks like linux still uses the same implementation ( Still the old version:
Comments on new version with option for 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. |
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... |
@djtm Hmm, I am only seeing |
I'm not 100% certain it's the same issue. I'll do more testing in the future, next week if all goes well. :) |
I am also seeing cookies with a Here is an example (from running Here is the same example base64 encoded: I am running Google chrome 54.0.2840.71 on Linux (ubuntu) |
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. |
I think starting Chrome with |
It looks like it's implemented here: https://github.com/bertrandom/chrome-cookies-secure/blob/master/index.js I'm guessing |
Affecting me too.. I've been trying to get the passwords out of |
Okay so I managed to extract the passwords from libsecret, they are in a service called "Chrome Safe Storage"
Hit me up if that doesn't work for you You can also use the command line:
|
Sweet, thanks. I tried and couldn't replicate the issue a couple days ago, but I forgot to check what version of Chromium I was running (couldn't be too old, a fresh Arch installation from scratch within the last month or two). When I get back to my Arch box I'll see if I can figure out how to reproduce, and if so how to incorporate this. Thanks again for the updates. |
@trideceth12: Could you send a pull request? Makes it easier to try this out. I'd be happy to try it.
|
I can't replicate the issue on Chromium 56.0.2924.87-1 on Arch Linux, cookies still have |
Which desktop environment do you use @n8henrie ? Depending on your environment, chrome might not find a keychain to store it's encryption key in. I think you get this in recent Ubuntu and Kubuntu. |
That could be it. I'm on wayland / sway. |
Hi! I'm new to GitHub and Python so please be nice :) I couldn't check in a Branch to create a Pull Request so here's what I did to make it work.
added after added before
added after added after
changed last decryption block to:
Just needs more testing to better handle exceptions and other platforms. @n8henrie - Issue occurred on Ubuntu 16.04.2 Desktop 64 bit with Google Chrome 57.0.2987.133 installed from Google. Let me know if you need more information! |
Great, thanks for getting me the version numbers. I'll see if I can spin up a VM and reproduce, if so will try to merge in that code. |
It would probably be better to check the desktop environment since that is the default for
|
Many thanks to @stat1c1c3au @trideceth12 -- been plugging away on Virtualbox / Ubuntu all day and have incorporated your code in a way that seems to work without breaking anything. https://github.com/n8henrie/pycookiecheat/tree/56ccaf345e1dcf74ff0db1af2dbd9a5eebb43721 NB: If using in a virtualenv, you apparently have to use the --system-site-packages flag in order to get access to the necessary |
Don't know if anybody has had time to test, but I'm going to go ahead and merge into master. I would really like to get better automated testing ideally using something like Selenium (especially since I'm not primarily on Linux, and when I am it's Arch, which is part of the reason I had such a hard time replicating this issue). I've started a docker-selenium branch to see if that might be a good solution, but I've never used either of these technologies, so would be happy to have help if anyone has more experience here. Specifically, would be nice to have CI testing on a Ubuntu 16.04 distro that uses the commits from this thread. |
Hey @n8henrie. Sorry, only just had a chance to try this out and have a couple of issues: 1/ Ubuntu It seems that it's not quite pulling the password out of the keyring. Debugging, I tracked it down to this code:
and had to change it to this to make it work:
2/ macOS Sierra 10.12.3 I couldn't upgrade using Ran into an issue when pip tried to uninstall the "six" package:
Is this normal? Thanks! |
Hmmm...
Unfortunately, I changed that line because the way it's working for you wasn't working for me. We'll have to track this down. gnome_keyring = service.get_collections()
unlocked_keyring = service.unlock_sync(gnome_keyring).unlocked[0] vs gnome_keyring = service.get_collections()[0]`
unlocked_keyring = service.unlock_sync([gnome_keyring]).unlocked[0] The way I have it, That said, the
I'd really rather you not install into the system site-packages. Please use a virtualenv. I think to find the source of the error you'd have to go through the dependencies and find which one / where they were trying to upgrade |
@stat1c1c3au Please test my latest dev commit: c55c9c7
|
@n8henrie latest dev commit is good 👍 and thanks for the tip on the virtualenv |
Excellent, thanks for the followup. I'll merge into master and re-release
likely tomorrow.
Nate
…On Tue, Apr 18, 2017 at 4:56 PM, stat1c1c3au ***@***.***> wrote:
@n8henrie <https://github.com/n8henrie> latest dev commit is good 👍
and thanks for the tip on the virtualenv
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABLYDIfvx95uxogWiztROLrgmw8syRZ2ks5rxT-7gaJpZM4J1dGI>
.
|
v0.3.5 is out on PyPI. Thanks for helping sort this out. |
The latest version of chromium has new cookies that start with 'v11' and wouldn't decrypt.
The text was updated successfully, but these errors were encountered: