Jonathan White

It is 'dangerous' to trust secret-tool implicitly because any adversary or malicious program would be using it to harvest credentials. So this is a hard problem to solve correctly.

Somewhat, perhaps a special case for explicit approvals of secret-tool parent process.

Well you leave it up to the user, just detect the process name (not path): > Warning: It looks like a process is using secret-tool, be sure you trust the...

Pretty clearly described here: https://github.com/keepassxreboot/keepassxc/issues/7571#issuecomment-1076921523

I don't really understand the need for _KeePassXC_ to be the broker for your env vars and binary running. This should be handled in a script that calls on KeePassXC...

Hmmm, well a script to achieve your example would look something like this (pseudocode): 1. Accept parameters to define keepassxc database and command to exec 2. Request database password 3....

Yes it would! I personally like the subcommand `exec` instead of `env`

Your shortcut choice is likely being used by some other program. Hover over the field highlighted red to see the error message. There isn't much we can do about this...

Check the windows event logs, maybe. There isn't anything we can do if we can't replicate the behavior. Check taskmanager to be certain that two KeePassXC instances aren't started.

You could try running a snapshot build, I made edits to this code tha hasn't landed in a release yet. https://snapshot.keepassxc.org