You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
apple_sep: J316s enrolment from 11.36 fails on 7.2 under the default xART guard #269
On J316s, an enrolment made under the 11.36 Touch ID release stops matching on 7.2 with the default xart_guard. Setting xart_guard=0 fixes it without re-enrolling.
Mac and installed build
MacBook Pro 16" M1 Pro (apple,j316s, profile T6000/J316s).
os-fw-version 13.5; system firmware iBoot mBoot-20457.41.3.
One finger enrolled on 2026-10-05 under 11.36, which has no guard.
Reproduction, expected result, and actual result
Enrol Touch ID under 11.36.
Boot 7.2 with the default xart_guard (level 1).
Run sudo with the enrolled finger.
Expected: the enrolment keeps working, or the driver says how to migrate.
Actual: the finger matches, then the guard refuses the post-match rewrite and every verify fails. All 14 session records count as foreign, because 11.36 kept no ownership list.
Workaround:options apple_sep xart_guard=0. The same enrolment restores and sudo accepts the finger.
This matches profile.rs (T6000), which says J316s keybag creation needs xart_guard=0. Re-enrolling with the guard on doesn't help either: xart_guard.rs blocks matching on cold-boot Macs.
Suggestion: when the keybag predates the guard list, log that xart_guard=0 is required on this profile. Today the only message is the refusal.
Relevant error lines
Default guard. This boot used 7.2.11.aurora8 with the 7.1 device trees, which don't affect the guard:
apple_sep: xART guard level 1: 14 session records exist, 0 created by Linux; the other 14 are protected
apple_sep: xART guard: refused to rewrite a kind-4 record this Linux install did not create
apple_sep 396400000.sep: verify: post-match identity-bag snapshot failed; the newly confirmed catacomb has no matching durable bag image
With xart_guard=0 on 7.2.11.aurora9:
apple_sep 396400000.sep: xART guard off: the enclave may rewrite any session record
apple_sep 396400000.sep: Touch ID: restored 1 enrolled identity/identities; enrolment survived reboot
changed the title [-]apple_sep: J316s (M1 Pro) upgraded from 11.36 loses Touch ID under the default xART guard; works with xart_guard=0[/-][+]apple_sep: J316s enrolment from 11.36 fails on 7.2 under the default xART guard[/+]on Oct 28, 2026
Same on a MacBook Pro 14" M1 Pro (apple,j314s, T6000 profile), migrated in place with omarchy-mac#690 from an aurora-sep install (linux-aurora 7.1.12.aurora2-20261015.19, two fingers enrolled on 2026-09-29) to linux-aurora 7.2.11.aurora16-1, omarchy-mac 0.2.3-2, libfprint 1.94.100-1.1, fprintd 1.94.5-2.
Default guard, first boot after the migration:
apple_sep: xART guard level 1: 11 session records exist, 0 created by Linux; the other 11 are protected
apple_sep: xART guard: refused to rewrite a kind-4 record this Linux install did not create
apple_sep 396400000.sep: verify: post-match identity-bag snapshot failed; the newly confirmed catacomb has no matching durable bag image
/var/lib/aurora-sep-xart-owned.bin was created empty, and diag/matching read blocked.
With options apple_sep xart_guard=0, after a reboot:
apple_sep 396400000.sep: xART guard off: the enclave may rewrite any session record
apple_sep 396400000.sep: Touch ID: restored 2 enrolled identity/identities; enrolment survived reboot
diag/matching is usable with 0 refusals. sudo accepted the finger, and the post-match keybag snapshot was written. No re-enrolment was needed.
+1 for the suggestion: a message naming xart_guard=0 when the keybag predates the list would have saved me the search. The migration tool could also mention it for aurora-sep Macs (omarchy-mac#778).
A draft that bears on this: #486 adds an opt-in xart_guard_pin=1 for cold-boot Macs. Instead of xart_guard=0, the guard stays on and the enclave may rewrite only the one pre-Linux SEP-xART locker that keybag creation reaches. Every other record from before Linux stays refused.
It is not tested on hardware. It builds and passes the KUnit suites under QEMU, and I have no Mac I can risk on it.
For anyone here already running a J316s or J314s with xart_guard=0: trying it means a Touch ID reset with /var/lib/aurora-sep-xart-owned.bin removed, so please read "Not tested" and "What a hardware run would need to show" in the pull request first. The caution in XART-SAFETY.md about macOS applies unchanged. A reply on whether the assumptions listed there match what you see on your Mac would already help, without running anything.
Activity
[-]apple_sep: J316s (M1 Pro) upgraded from 11.36 loses Touch ID under the default xART guard; works with xart_guard=0[/-][+]apple_sep: J316s enrolment from 11.36 fails on 7.2 under the default xART guard[/+]cb2206 commentedon Nov 11, 2026
Same on a MacBook Pro 14" M1 Pro (
apple,j314s, T6000 profile), migrated in place with omarchy-mac#690 from an aurora-sep install (linux-aurora 7.1.12.aurora2-20261015.19, two fingers enrolled on 2026-09-29) tolinux-aurora 7.2.11.aurora16-1,omarchy-mac 0.2.3-2,libfprint 1.94.100-1.1,fprintd 1.94.5-2.Default guard, first boot after the migration:
/var/lib/aurora-sep-xart-owned.binwas created empty, anddiag/matchingreadblocked.With
options apple_sep xart_guard=0, after a reboot:diag/matchingisusablewith 0 refusals.sudoaccepted the finger, and the post-match keybag snapshot was written. No re-enrolment was needed.+1 for the suggestion: a message naming
xart_guard=0when the keybag predates the list would have saved me the search. The migration tool could also mention it for aurora-sep Macs (omarchy-mac#778).poulguoskov commentedon Nov 15, 2026
A draft that bears on this: #486 adds an opt-in
xart_guard_pin=1for cold-boot Macs. Instead ofxart_guard=0, the guard stays on and the enclave may rewrite only the one pre-Linux SEP-xART locker that keybag creation reaches. Every other record from before Linux stays refused.It is not tested on hardware. It builds and passes the KUnit suites under QEMU, and I have no Mac I can risk on it.
For anyone here already running a J316s or J314s with
xart_guard=0: trying it means a Touch ID reset with/var/lib/aurora-sep-xart-owned.binremoved, so please read "Not tested" and "What a hardware run would need to show" in the pull request first. The caution in XART-SAFETY.md about macOS applies unchanged. A reply on whether the assumptions listed there match what you see on your Mac would already help, without running anything.