6ccd289691
Fingerprint PAM module can have multiple failures during a runtime and we rely on the pam module configuration for the maximum allowed retries. However, while that setting should be always followed, we should never ignore the login-screen's allowed-failures setting that can provide a lower value. So, once we have a fingerprint failure let's count it to increase our internal fail counter, and when we've reached the limit we can emit a verification-failed signal to our clients. As per this we need also to ignore any further 'info' messages that we could receive from the fingerprint service, as it may be configured to handle more retries than us and they might arrive before we have cancelled the verification session. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1652> |
||
|---|---|---|
| .. | ||
| authPrompt.js | ||
| batch.js | ||
| credentialManager.js | ||
| loginDialog.js | ||
| oVirt.js | ||
| realmd.js | ||
| util.js | ||
| vmware.js | ||