-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CLI: provide password via environment variable #3934
Comments
That seems extraordinarily insecure. Just cache the password in a local variable |
It's up to the user of it to use it in a secure or unsecure way I'd say. I don't see an issue in reading the password from CLI and use it in a script, it will only be stored in memory for the runtime of the script. |
We also have a open mode now in 2.5 that keeps the database open |
sounds nice, can you point me to how to use it? Was looking for something like that, but didn't find anything in the help. |
|
For people reading this issue:
|
^ Just make sure to clean up the trails. |
Use environment variable to unlock database
Summary
Currently, when using
keepassxc-cli
in scripts multiple times, I have to enter the password each time. I see that a cache as mentioned in this issue would mean a huge refactoring.As a first easier step, I would like to be able to provide the password in an environment variable, so I can read it once at the beginning of my script and
keepassxc-cli
automatically uses it if the variable is set (guess that would be somewhere here).I thought about implementing it right away, but I'd like to open a discussion around naming and usefulness.
Desired Behavior
Possible Solution
read environment variable (proposal:
KEEPASS_DB_PASSWORD
) here and use it to unlock database if set. If not, ask as beforeContext
I want to execute multiple keepassxc-cli commands in one script without entering the password multiple times.
The text was updated successfully, but these errors were encountered: