Repository navigation
Build libfprint-git for aarch64 with the Apple Touch ID driver - #806
Conversation
Omarchy's fingerprint setup installs libfprint-git, which built for x86_64 only, so an Apple Silicon Mac had no Omarchy libfprint at all. It now builds for aarch64 too, and there it carries Chris Kearney's aurora driver for Touch ID, which the aurora kernel's Secure Enclave driver exposes as /dev/sep-bio. The x86_64 build applies nothing new. The patch is his libfprint-1.94.100-apple-sep.patch from iconidentify/aurora-linux sep-7.1.12.aurora2-11.35, less its tests/meson.build hunk: libfprint 3f1e2817, already in this pin, made the same fix. The libfprint provide is now versioned, so aurora-touchid's libfprint>=1.94.100-1.1 still resolves when this replaces his build. Built on an M2 Max: 131 libfprint tests pass, none fail. Co-authored-by: Chris Kearney <303316+iconidentify@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
@ryanrhughes @powderluv could one of you review this? You've both worked on the libfprint-git recipe. It adds the aarch64 build with the Touch ID driver; x86_64 only gains the versioned provide. |
The setup kept a platform's own libfprint because no Omarchy libfprint carried a Mac's Touch ID driver. omarchy-pkgs' libfprint-git now builds for aarch64 with that driver (omacom/omarchy-pkgs#806), so the setup's libfprint-git is the right library on a Mac too, and this change only teaches omarchy-hw-fingerprint the platform's readers. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
@scottjones reviewed at CI never built it. Both build jobs died in the builder image on The versioned provide is fine: Before merge:
Nits: the patch has Order across the three: this one first, once it builds and is published for aarch64; omacom/omarchy-mac#694 can land alongside; omacom/omarchy-mac-pkgs#12 last. |
|
Follow-up after a second review at Builds on aarch64. Three new points:
|
…e it Marcelo's review: the docs said a file must read "exactly" its value, but the comparison drops trailing newlines, a space splits a line's fields and the file is read as the session user; they now say so. A platform file that matches nothing must never hide a USB reader, so the test now pairs one with a real USB reader both ways. lifecycle-dispatch.md lists the file with the others, and file-layout.md no longer says aarch64 libfprint-git carries the Touch ID driver before omacom/omarchy-pkgs#806 publishes it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Thanks. In
Also confirmed on hardware: installed in place of Chris's own build, this package enrolls and verifies. Pushing re-runs the build the keyserver killed. |
Summary
Omarchy's fingerprint setup installs
libfprint-git, which built for x86_64 only, so Apple Silicon Macs had no Omarchy libfprint. It now builds for aarch64 too, and there it carries @iconidentify (Chris Kearney)'s aurora driver for Touch ID, which the aurora kernel's Secure Enclave driver exposes as/dev/sep-bio. The x86_64 build applies nothing new.The patch is Chris's
libfprint-1.94.100-apple-sep.patch(iconidentify/aurora-linuxsep-7.1.12.aurora2-11.35), less itstests/meson.buildhunk: libfprint3f1e2817, already in this pin, made the same fix. Besides the driver it adds 58 lines to libfprint's core, a generic "reader behind a kernel misc device" lookup that only a driver asking for it uses.Evidence
Built on an M2 Max: 131 libfprint tests pass, 0 fail. Installed in place of Chris's own build,
fprintd-verifymatches with the existing enrollment. Part of making Touch ID work out of the box with omacom/omarchy-mac#694 and omacom/omarchy-mac-pkgs#12.Merge Danger
Door: two-way
Blast Radius: aarch64 (new); x86_64 rebuild with only a versioned provide
🤖 Generated with Claude Code