fprintd_shim_lock_screen_SUCCESS.txt 3.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. Phase 1 fprintd shim — end-to-end success evidence
  2. ===================================================
  3. Date: 2026-10-15
  4. Host: lunar (Arch, GNOME Shell 51 / GDM 51, Wayland, session id 3)
  5. Installed service
  6. -----------------
  7. /etc/systemd/system/fprintd.service -> work/fprintd-shim/fprintd.service
  8. Active: active (running) — serves net.reactivated.Fprint on the system bus
  9. (work/fprintd-shim/install.sh, authorized via the fingerprint reader itself)
  10. CLI (/usr/bin/fprintd-list)
  11. ---------------------------
  12. $ fprintd-list nebulon
  13. found 1 devices
  14. Device at /net/reactivated/Fprint/Device/0
  15. Using device /net/reactivated/Fprint/Device/0
  16. Fingerprints for user nebulon on Synaptics 06cb:0081 (press):
  17. - #0: right-index-finger
  18. Shell reader detection (same calls as libshell-51.so -> fingerprintManager.js)
  19. ------------------------------------------------------------------------------
  20. GetDefaultDevice -> /net/reactivated/Fprint/Device/0 (service auto-started)
  21. scan-type -> press => GNOME reader type PRESS (fingerprint mechanism enabled)
  22. fprintd-verify (CLI match path)
  23. -------------------------------
  24. $ timeout 50 fprintd-verify -f any nebulon
  25. Using device /net/reactivated/Fprint/Device/0
  26. Listing enrolled fingers: - #0: right-index-finger
  27. Verify started! / Verifying: right-index-finger
  28. Verify result: verify-match (done)
  29. fprintd-verify rc=0
  30. (An earlier run matched but exited 1 because VerifyStop returned
  31. NoActionInProgress after the terminal result; the shim now keeps fprintd's
  32. "action in progress" semantics until VerifyStop/Release.)
  33. Rollback test (uninstall -> stock fprintd -> reinstall)
  34. -------------------------------------------------------
  35. $ sudo work/fprintd-shim/uninstall.sh; fprintd-list nebulon
  36. No devices available <- stock fprintd took over
  37. $ sudo work/fprintd-shim/install.sh; fprintd-list nebulon
  38. Fingerprints for user nebulon on Synaptics 06cb:0081 (press):
  39. - #0: right-index-finger
  40. pam_fprintd end-to-end (isolated, pam_start_confdir)
  41. ----------------------------------------------------
  42. $ /tmp/opencode/pamtest3 -d /tmp/opencode/pam-confdir -s fprintd-test nebulon
  43. service=fprintd-test user=nebulon confdir=/tmp/opencode/pam-confdir
  44. (touch the sensor)
  45. pam_authenticate => 0 (Success)
  46. Real lock screen (loginctl lock-session 3, then touch)
  47. ------------------------------------------------------
  48. journalctl -u fprintd:
  49. 2026-10-15T11:59:01+02:00 fprintd-shim: INFO: claim by :1.2046 for user nebulon
  50. 2026-10-15T11:59:06+02:00 fprintd-shim: INFO: verify[1]: Fingerprint matched.
  51. 2026-10-15T11:59:06+02:00 fprintd-shim: INFO: claiming client :1.2046 vanished, releasing device
  52. ...and the session unlocked (loginctl LockedHint: yes -> no) without a
  53. password entry: pam_fprintd disconnects on PAM_SUCCESS (the shim releases the
  54. claim via NameOwnerChanged, exactly like fprintd's client-vanished handling).
  55. API semantics regression (session bus, no touch)
  56. ------------------------------------------------
  57. work/fprintd-shim/apitest.py -> all checks passed:
  58. GetDevices, ListEnrolledFingers (enrolled vs other user), Claim twice ->
  59. AlreadyInUse, VerifyStart unclaimed -> ClaimDevice, VerifyStart/Release from
  60. non-claimer -> AlreadyInUse, unenrolled finger -> NoEnrolledPrints, claim
  61. auto-release when the claiming client disconnects.
  62. Operational notes
  63. -----------------
  64. - Earlier failed `sudo` attempts (fingerprint auth misses) tripped
  65. pam_faillock ("User nebulon is temporarily locked out due to 3 consecutive
  66. failed login attempts") which blocked the gdm-fingerprint PAM stack before
  67. pam_fprintd ran. Reset with: sudo faillock --user nebulon --reset
  68. - sudo / polkit are unchanged and still use work/pam/pam_fp.so.
  69. - work/fp-verify.sh takes an flock so concurrent verifications (sudo +
  70. lock screen) serialize on the USB device.