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

KeePassXC compatibility #42

Closed
rugk opened this issue Mar 16, 2018 · 4 comments
Closed

KeePassXC compatibility #42

rugk opened this issue Mar 16, 2018 · 4 comments
Labels

Comments

@rugk
Copy link

rugk commented Mar 16, 2018

The new version of KeePassXC has been released and it features some optional changes of the key file, mostly encryption-related. v2.3.0 now supports "KDBX 4.0, Argon2 and ChaCha20".

So is this app already compatible or does it need to be adjusted?
In any case, I'd advice you to advertise your app also with "KeePassXC compatible" (in Readme, app description, etc.) so users know they can use it with KeePassXC.

@J-Jamet
Copy link
Member

J-Jamet commented Mar 16, 2018

It need to be adjusted, some settings can't work for now with this new database format and I need to refactor some old code to make it compatible.
I'll add compatibility in the description when it will be refactored.
(link to #9, #29)

@J-Jamet J-Jamet added the bug label Mar 16, 2018
@rugk
Copy link
Author

rugk commented Mar 16, 2018

Hmm, but is it possible to open a database, at least?

The tickets you linked, only apply to some specific cases, like creating a database with Argon2. It would, however, e.g. already be good if you could open and edit Argon2 databases.

@gerardo-junior
Copy link

+1

@J-Jamet
Copy link
Member

J-Jamet commented Mar 17, 2018

Yes, the Argon2 database can be opened and edited, the algorithm is in the code. But before making any adjustments, I need to refactor all the code of the parser and make the tests. (EDIT : Chacha20 is implemented and works fine). It was created in the main project forked.

It works with C and JNI code, and the parser code does not separate the concepts (so not so easy). I have to separate each concept, then I can manage the options and parameters of each algorithm.
That's why I linked it to other problems.

I try to be quick to solve all the other worries before doing this big piece.

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

No branches or pull requests

3 participants