https://bugzilla.novell.com/show_bug.cgi?id=441144
User lavrinenko_alex@mail.ru added comment
https://bugzilla.novell.com/show_bug.cgi?id=441144#c21
Alexander Lavirnenko changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lavrinenko_alex@mail.ru
--- Comment #21 from Alexander Lavirnenko 2008-11-26 00:50:22 MST ---
Regarding KDE3: both KDM3 and kscreensaver3 support and work with fp-readers.
At least it works for me with pam_fprint (AuthenTec AES2501 USB scanner found
on HP laptops). The way it is implemented in KDE3 (and maybe in KDE4 as well)
is a bit funny. Actually in order to authorize with fp, user needs to choose
login name and press <enter> on empty password field at kdm login screen, or
press <enter> after kscreensaver prompts for password to unlock. After <enter>
is pressed popup appears offering to scan <enrolled finger> on scanner.
Pressing <OK> button of this popup before actual finger scan leads to some sort
of kdm/kscreensaver lockup, but this means that fp-scanner is waiting for
finger image input. Just scanning finger afterwards (if successfull) leads to
session unlock. But whenever i enter correct password first, and press <enter>,
i still get finger scan request popup, that should not happen with correct
password entered. So, kde3/4 fingerperint support bugs are as follows:
1. if PAM is set to support fingerprint scans, kdm/kscreensaver should offer
this auth type to user immediately, without waiting for user to press <enter>,
with no UI lockups;
2. if finger scan is successfull, kdm/kscreensaver should log in/unlock
immediately without any unnecessary keypresses;
3. if correct password is entered and <enter> pressed without any finger scan,
kdm/kscreensaver should accept this and log in;
4. if INCORRECT password is entered, kdm/kscreensaver should not wait for
finger scan, but fail this attempt like it does now with wrong password entered
and no fp enabled.
I will try to create mockups for kdm and screensaver and attach them later
here.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.