[FEATURE] Fingerprint sudo authentication #124
Description
Problem Description
Right now there isn't (as far as I can tell) direct support for using the fingerprint instead of the password upon installing packages. I usually just press enter without a password and let the terminal ask me for it in the next modal. Unfortunately the password input can't be disabled using the use_passwordless_sudo setting because it checks with the "sudo -n true" command as a failsafe.
Proposed Solution
I don't know if it's possible to check if fingerprint authentication is set up. fprintd-list $USER does list enrolled fingerprints if it helps, but it has to be set up as sufficient in /etc/pam.d for it to be used.
I realize this is probably impossible to work on for anyone without a fingerprint reader, I can give it a shot myself with some guidance.
Use Cases
Describe specific scenarios where this feature would be useful:
- Laptops usually have a fingerprint reader nowadays.
Alternatives Considered
- A setting that force-skips the password input, trusting that the user has fingerprint auth set up in pam would work, though it seems messy. I don't think it would hurt in any way however.
- Perhaps polkit agent integration? This seems a bit overkill.
UX/Behavior Details
- How should this feature work from a user's perspective?
-
- Best case scenario a NerdFont fingerprint icon (or just text indicating fingerprint authentication) would be shown next to the password input to indicate it can be used.
- What keyboard shortcuts (if any) should be used?
-
- None.
- Should this be configurable? If so, what settings would be needed?
-
- If it would be possible to check for the fingerprint auth automatically then no. Otherwise, an opt-in setting.
- Any edge cases or special considerations?
-
- Enrolled fprintd fingerprint without the pam.d set up correctly.
Additional Context
- Is this feature related to an existing issue or discussion? - No
- Does this align with Pacsea's keyboard-first philosophy? - Yes
- Any compatibility concerns (Wayland/X11, different terminals, etc.)? - I wouldn't imagine so
Checklist
- I have searched existing issues and discussions to ensure this hasn't been suggested before
- I have checked the Roadmap and What's Next discussions
- I have considered how this feature would integrate with existing functionality