pbkhrv / ulauncher-keepassxc Goto Github PK

It would be great to be able to handle multiple databases (maybe each of them which a dedicated search string configured).

I've tried moving my kdbx, I've tried renaming it, I've tried creating a symlink with the default name. No matter what I do, I get "cannot find the database file."

We could troubleshoot this, but it seems more sensible to suggest a file chooser.

Please upvote if you would like this feature.

The "Unlock KeePassXC database" message should show the database file path in the description

...because path expansion fix...

The "Cannot find the database file" item should show the database file path in the description

should restore the query arg, just like we do around "check_and_reset_search_restore"

use a nice back-arrow icon from nounproject

In the last few days I started having a problem searching my keepass database using the keepass search extension. I attached a screenshot of the error message. The error is resolved after changing "locate" to "search" on line 127 of keepassxc_db.py file.
I apologize for not using the proper formatting, as I'm not a coder. Just want to let the creator know so the change can be made if needed

.

Handle preference update event and un-initialize the database object.

right now cli is called for every entry attribute. Call it once with a bunch of attributes as a list and parse results. ("Notes" should be the last one because multiline)

https://keepassxc.org/blog/2019-10-26-2.5.0-released/

Use case:
I have some websites with multiple accounts and the entries all appear the same, so I don't know which account I am selecting.

Please upvote if you'd like this feature.

• Every time an entry is "activated", add it to the top of "recently accessed entries" list. Dedup the list.
• when no query arg is specified AND database is unlocked, show recently accessed entries

Doing our own searching of entry names requires having fast access to the full list of entries stored in a particular database. How?

• Option 1: run "keepassxc-cli ls" every time, parse the output, run regex on it
• Option 2: run "keepassxc-cli ls" periodically, maintain the entry list in memory and search through that instead

The Plan:

• Implement and test option 1 for speed and responsiveness
• IF option 1 proves to be too slow, implement option 2

Option 2 implementation:

• Run "ls" when database is unlocked
• Run "ls" whenever database file changes - launch a separate monitor thread when extension starts up and use pyinotify to watch the database file for changes
• Compile a regex based on query, then call .search on it: "gith wor" -> r"gith.*?wor"

Search results show up slow-ish, which is especially visible when you select an entry, then press backspace to return to search results

a cache of about 60 seconds should be enough?

Simplest workflow:

• User enters "kp new entry title"
• Ext displays search results and "Generate and save password / Create 'new entry title'"
• User selects "Generate..." and presses Enter
• Ext runs keepassxc-cli add -g database_path "new entry title"
• Ext copies the new password to the clipboard

(Password length and generation options can be made configurable, passed as CLI options)

One downside of this approach is that there's not a straightforward way to specify username or URL for the new entry. There might be a ulauncher-centric solution for that, need to think about it.