-
Notifications
You must be signed in to change notification settings - Fork 6
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
Passwords appear blank #1
Comments
running windows .exe from releases. |
@Txoka the encryption or database format probably changed. I don't have a windows PC on hand to test, so you'll have to debug the new format yourself. If you're willing, you could create a new profile, save only one (not your real one!) password, and send me the corresponding "Login Data" sqlite file, so I can take a look at it. |
Sorry, i have been testing, not all passwords appear blank, only some of them, for example gmail password appeared blank on every test other passwords are exported correctly. I will see if i can send you that. Here it is: the file containing encrypted passwords and the passwords.csv that does not have the password i tried to export |
Hm... seems like there is some data in there alright. The decoding happens here: https://github.com/cfstras/chromecsv/blob/master/crypt_windows.go The function also doesn't evaluate the return code... it should return a boolean, that would be the first thing to check. |
Looking at the current chromium source... https://source.chromium.org/chromium/chromium/src/+/master:components/os_crypt/os_crypt_win.cc;drc=8e721d89fb9dbf5ed62cfa43f44d3d27ee1776de;bpv=1;bpt=1;l=33?originalUrl=https:%2F%2Fcs.chromium.org%2F It seems there is a new format. Your data has the prefix "v10" in which case the function |
since g_use_mock_key is set to false i think it comes from here but i do not totally understand it sorry
Also i can't seem to discover which passwords i can export using Windows api and which not. |
|
The execution works fine, but the passwords are missing in the .csv
The text was updated successfully, but these errors were encountered: