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

libkeepass rewrite #1

Open
Evidlo opened this issue Jun 9, 2018 · 2 comments
Open

libkeepass rewrite #1

Evidlo opened this issue Jun 9, 2018 · 2 comments

Comments

@Evidlo
Copy link
Member

Evidlo commented Jun 9, 2018

@pschmitt @crass

I've been working on a complete rewrite to add support for KDBX4 (and KDBX3) and shrink down the codebase.

Things to note:

  • only tested on python3
  • no twofish support yet
  • no entry unprotecting yet fixed
  • kdbx4 seems to use some new binary format for storing dates? all my date fields look similar to 1M100A4AAAA= fixed in pykeepass
    edit: see here

Also, getting pykeepass working with it was pretty trivial. See the libkeepass_proto branch:
https://github.com/Evidlo/pykeepass

Let me know what you think.

@Evidlo
Copy link
Member Author

Evidlo commented Jun 11, 2018

Should protected/unprotected opening even be configurable? Right now it always opens unprotected. We can't have any memory security with python anyway.

@Evidlo
Copy link
Member Author

Evidlo commented Jun 19, 2018

@pschmitt How do you feel about possibly merging pykeepass and libkeepass? I think there's no practical reason for the codebases to be separate anymore, and anyone who needs low-level database manipulation still has access to PyKeePass.kdb object.

Also @firecat53 would probably be interested in this thread.

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

No branches or pull requests

1 participant