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

When sudo is configured to ask for a fingerprint, suda halts for a long time #56

Open
LyesSaadi opened this issue Jan 19, 2023 · 2 comments

Comments

@LyesSaadi
Copy link

LyesSaadi commented Jan 19, 2023

Using a fingerprint "unhalts" suda.

It seems sudo is waiting for a fingerprint despite writing a password.

@lambdalisue
Copy link
Owner

Need minimal vimrc and reproduction steps.

@Marlstar
Copy link

Hi! I have the same issue.

  • To reproduce, enroll your fingerprint with a compatible fingerprint reader. This can be done using fprintd-enroll, which required fprintd to be installed.
  • Enable sudo fingerprint authentication by running sudo authselect enable-feature with-fingerprint
  • :SudaWrite a file

Suda will then hang waiting for a fingerprint. Notably, if an incorrect password is provided but a fingerprint is used, authentication will succeed. If a fingerprint is not provided, Suda will hang until fingerprint authentication times out, at which point it will continue as normal.
While this is a system configuration issue, it would be nice if Suda provided some indication that the system is waiting for a fingerprint to continue with the authentication process.
Additionally, a config option could be provided to allow authentication to succeed using a fingerprint without having to input a password into Suda.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants