-
Notifications
You must be signed in to change notification settings - Fork 97
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
cannot open db file #3
Comments
ok copy the "Login Data" file to the same directory as where your tool is located then rename it to a single word named file example: "Logins", "Winter", "POwned" "LoginDATA" Assuming you have the "LoginDATA" (or whatever you named the file) in the same directory as this tool |
ty mate it works!!!
LD
2017-09-08 8:15 GMT+02:00 Sp3c7R3 <[email protected]>:
… ok copy the "Login Data" file to the same directory as where your tool is
located then rename it to a single word named file example: "Logins",
"Winter", "POwned" "LoginDATA"
Assuming you have the "LoginDATA" (or whatever you named the file) in the
same directory as this tool
Run the command:
chrome_decrypt.exe LoginDATA
(You may change LoginDATA with whatever you named the login data file)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASmXxB22DnIXTRuCKtSgpIUFNImpzEKjks5sgNuOgaJpZM4O2ci2>
.
|
This is caused because Chrome is saved under C:\Users*****\AppData\Local** path not under C:\Users*****\AppData\Roaming** try to change the python file code to something like this and execute it eg: path = str(w[0]) + '\..\..\Local\Google\Chrome\User Data\Default\Login Data' its should work. |
i can fix it |
path = str(w [0])。。。。 |
can someone like do it for me lmao |
hi all,
why this happens?
[+] Opening C:\Users*******\AppData\Roaming\Google\Chrome\User Data\Default\Login Data
[-] unable to open database file
running exe file
in 2 different pc's i have the same error
please help me
ty
The text was updated successfully, but these errors were encountered: