New features

[Evidlo]

• tests
• add mv/rename for command renaming
• non-interactive add
• allow custom fields for add command
• libkeepass is slow. cache all XML in ~/.cache/passhole_cache argon2 KDF is much faster than AES KDF, once support is added in libkeepass
• add edit for minor changes to existing entries
• add grep command
• alias ls to list, rm to remove
• [ ] auto create separate gpg-key? maybe use a background thread to cache password like keepmenu?
• add -f, --force option to rm to force deletion of nonempty groups
• add --username argument to type (and ls?) to show username in parenthesis after the path
• [ ] rewrite using Click (not possible, see issue)
  • [ ] investigate Click color output features
• info command to dump database info (encryption, kdf method, version, size, etc.)
• dump command to dump database xml
• store databases in background thread
• entry/group autocompletion (requires background thread)
• auto type sequences
• attachments
• add un-hide password -u to show command
• add password to config, add --password
• get rpyc branch working with pykeepass tests
• password regeneration, move old password to history
• display password history
• git support? initialized databases might be created inside a repo and prompt for adding remote server
• regenerating passwords
• database backup copy after successful opening
• set command for canging database settings

[whwright]

Would you like help with any of these?

[Evidlo]

Sure!

Two issues that I think are most important:

1. Adding tests. The current code is not really testable because there are print statements and input() and sys.exit() scattered throughout. This might not be a big deal so long as the print statements are replaced with log. See here, here, and here.
2. Background thread. By keeping the database open in a background thread for N minutes, we get a huge speed boost because passhole doesn't have to reopen the database for every operation. We also don't have to rely on gpg/gpgme as a dependency anymore. This brings up some issues though:
   • We need to reload the database in the background thread if an external change is detected. Probably not too hard.
   • What goes in the background thread and how do we communicate with the foreground?