Skip to content
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

Problem using keyfile 4 kdbx #337

Closed
nealmibe opened this issue Sep 7, 2019 · 3 comments
Closed

Problem using keyfile 4 kdbx #337

nealmibe opened this issue Sep 7, 2019 · 3 comments

Comments

@nealmibe
Copy link

nealmibe commented Sep 7, 2019

Hello Tusk-Team,

I'm experiencing problems using a version 4.kdbx file in Keepass Tusk for Chrome.

The file is generated through an CSV-import via Keepass XC and saved as 4-kdbx file. This file can't be opened in Keepass Tusk for Chrome. But the same procedure with a 3.1-kdbx file works well.

I attached two sample files (3.1-kdbx and 4-kdbx version) as a zip file:
sample.zip

I used the generic CSV file from the website auf Keepass: https://keepass.info/help/base/importexport.html

Both files are protected with the password '1234'. Both can be opened in Keepass XC.

Maybe you have an idea what could be the mistake? Thank you for your time.

Regards,

Neal

@vii1
Copy link

vii1 commented Sep 8, 2019

New user to KeePass here. I have a v4 kbdx (w/ master password, no keyfile) and Tusk fails with "Incorrect password or keyfile". Might be this same problem?

@subdavis
Copy link
Owner

subdavis commented Aug 8, 2024

Need to look at upgrading Argon2 implementation, I have several databases that I can use to reproduce this.

@subdavis
Copy link
Owner

Upgraded to the newest version of argon2 wasm, confirmed kdbx4 is working. I'd like to move this into a service worker, but that can be a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants