https://bugs.kde.org/show_bug.cgi?id=494168
Marco G <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Marco G <[email protected]> --- Theoretical there are several aproaches to this: Let's say we initiated a gui auth dialog and the fingerprint is active waiting now for the user to auth via fingerprint because this is firt pam rule. The Dialog still shows the password prompt but actually for now (1. PAM) only care about fingerprint. 1. if the user still decide to enter the password the OK button or ENTER if pass !empty should initiate a cancle for the still pending 1. pam rule fingerprintd wait and then we have password as fallback 2. alternative redesign the dialog that we dont even display the password prompt but only a message waiting for fingerprint and a cancle option (which is not present there currently) if cancle we present the classical auth dialog 3. alternative allow a setting somewhere in polkit to let the user set a own timout for the fingerprint to fail. For me I would set this to something as low as 5s so I still have a reasonable amount of time to validate via finger or fallback to to password. Why all this? Well some of us work in the field as technician or whatever field IT. You sometimes have to wear protective gloves and with them it is impossible to continue on the auth diagloge currently because you cannot even trigger a false fingerprint. Only option is to disble fingerprint auth in pam right now. A short timeout or a sane fallback methode would circumvent this. Unfortunately just hitting ESC is not a solution because it will close the dialog and end the auth process with false. Having ESC not close the full dialog but just skip to the next pam step would also an option. But I am not a core developer so I can't judge if this is even possible. Thanks -- You are receiving this mail because: You are watching all bug changes.
