DmitryOb
commented
1 year ago @fossfreedom @JoshStrobl Do we have now any temporary workaround for custom implementation fingerprint login via budgie-control-center + lightDM ?
I want too this feature in budgie-control-center:
fossfreedom
Current budgie-control-center version
v1.1.1
Use-cases
Where linux fingerprint devices are supported, some login managers such as GDM3 have direct support built in to enable login.
Some login managers such as lightdm need administrator action to enable login.
Budgie could support fingerprint login via BCC with a tweak and a tuck.
Proposal
In GNOME Control Center - once a fingerprint device is detected, a new option in the Users Panel appears enabling the administrator to enrol fingerprints.
This is not currently available in BCC without using GDM3 since the code is looking for a schema key that is delivered only in GDM3.
The proposal here is to enable fingerprint enrolling via the BCC users panel for our recommended login manager - lightDM.
The suggestion here is to remove the check for the enable-fingerprint-authentication key in the GDM login schema and instead substitute it for a check if a known fingerprint device is plugged in (code is already there for this check).
This leaves the issue how to inform the user whether they have enabled lightdm (via PAM) for fprintd <-- the module that does the authentication.
The above enables fprintd globally i.e. not specific to lightdm/gnome-screensaver. It writes to /etc/pam.d/common-auth
Adding the above line to /etc/pam.d/lightdm and /etc/pam.d/gnome-screensaver directly before the "@include common-auth" limits fingerprint login to both lightdm and gnome-screensaver.
GDM3 provides the PAM fprintd configuration out of the box. LightDM doesnt.
I don't know of a way to test if fprintd has been enabled in PAM. We can either ignore this particular issue and assume the user knows how to-do things. Or somehow give the user via the fingerprint dialog some sort of hint what they need to-do.
Thoughts.
References
N/A