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

FR: Retrieve custom attributes #2

Open
IOIO72 opened this issue Dec 6, 2021 · 3 comments
Open

FR: Retrieve custom attributes #2

IOIO72 opened this issue Dec 6, 2021 · 3 comments

Comments

@IOIO72
Copy link

IOIO72 commented Dec 6, 2021

It would be helpful to be able to retrieve custom attributes.

@lxbrvr
Copy link
Owner

lxbrvr commented Apr 10, 2022

@IOIO72

It would be helpful, but the workflow uses the keepassxc-cli show command and unfortunately it does not allow to get custom attributes. Only specific attributes need to be specified there. For example, to fetch an username and a password, the workflow runs the command keepassxc-cli show -a username -a password ....

There is one way to get the custom attributes, but I'm not sure about it yet. The way is to completely export the data from the KeepassXC database and collect this information.

In general, there is already the issue on KeepassXC issues. I hope they will allow us to fetch these attributes in near future.

@IOIO72
Copy link
Author

IOIO72 commented Apr 11, 2022

Thank you for the investigation.
I'm not sure, if the following idea is a good idea:
Is it possible to manually set up some attributes, which one uses in general?

@lxbrvr
Copy link
Owner

lxbrvr commented Apr 13, 2022

The idea is good but...

The workflow uses the keepassxc-cli tool and it searches for entries by their paths. For example dir1/dir2/entry. Now let's imagine the next case.

  1. A user adds some custom attribute using the workflow for some KeepassXC entry. Let's call it as "Entry A" and the path to it is dir1/dir2/Entry A.
  2. The user opens the KeepassXC UI and renames the "Entry A" to "Entry B". The path is now dir1/dir2/Entry B.

After the second step the workflow shows "Entry B", but the custom attribute was added for "Entry A". And the custom attribute now is the redundant. It is not expected behavior for users. Of course we can show the user that there are such redundancies and it's necessary to do something with them. For example, delete or bind them with new KeepassXC entries. But should we make it so complicated?

Unfortunately the KeepassXC CLI doesn't tell us about any unique identifiers which exist during the whole entry life (movement, renaming etc). We have only paths.

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

2 participants