scottjones wrote that setup told everyone to keep moving a finger around the sensor and printed fprintd's raw enroll-stage-passed lines. He wrote that on a press sensor like a Mac's Touch ID, that read as one touch and wait, and that enrollment timed out a minute later.

The pull request says setup asks fprintd for the reader's scan type, and that a press sensor is told to touch, lift and touch again until it says Enrolled. The pull request says that when fprintd cannot say the scan type, the prompts say "touch or swipe".

scottjones wrote that sudo is authenticated up front, and that with fingerprint sudo already set up, its own touch was being taken as the first sample. The pull request says a failed verify exits 1, and that PAM is still written only after a print verifies.

scottjones wrote that on an M2 Max, fprintd reports the reader as "Apple secure enclave fingerprint sensor" with scan type press, which is the Touch ID path. He wrote that swipe readers, other readers that identify, and the PAM success path are covered only by the stubbed tests. He wrote that he has not run setup end to end on this branch, since that writes PAM.