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

Biometrics Prompt Should Not Ask For Permission Twice #142

Open
quexten opened this issue Mar 16, 2024 · 2 comments
Open

Biometrics Prompt Should Not Ask For Permission Twice #142

quexten opened this issue Mar 16, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@quexten
Copy link
Owner

quexten commented Mar 16, 2024

Right now there are 2 prompts, one for authentication (polkit), and one for approval. It would be nicer to just have 1 prompt. Some polkit (or pam) authentication modules don't require interaction (f.e howdy). I'm not sure if we can detect this.

If we just accept this, then the "risk" would be that, using a no-interaction required auth method, a malicious app could trigger the biometrics prompt, and instantly get the vault user key from goldwarden, while the user is sitting in front of their computer.

@quexten
Copy link
Owner Author

quexten commented Mar 16, 2024

For the record, I'm personally fine with either as long as the "risk" is described clearly to the user. Malicious applications on the same device are only a secondary goal to strive towards where reasonable. In this case, the usability is significantly hurt.

@c4tz
Copy link
Contributor

c4tz commented Mar 16, 2024

I also think the risk (especially when using howdy, which itself states it is unsafe) is ok.

I think these would be possible options to handle this:

  • Make the approval pop-up optional (e.g. by having a config entry / env var), so users with/without concerns could opt-in/out of having to "double" approve all requests
  • Do the same as howdy and state in the docs that users who do not want to take this risk can add another (required) PAM/Polkit verification step in form of a password/PIN/etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants