Repository navigation
Conversation
Carry the public diff of pending linux-aurora PR 234 at accecc6 as an explicit dependency for the J613 existing-bag test series. Unreadable state must not select fresh identity or replacement-key paths. This is not a second submission of that change. Signed-off-by: Satya Benson <satya@benson.earth>
Keep the existing T8122 transport and sensor profile. On the owner-qualified OS-firmware lane, refuse writable attachment without the boot-forwarded identity and guard, and fail closed on host-store/index read errors. Add opt-outs for trusted-key and FileVault API registration with existing defaults preserved. No new provisioning or firmware protocol is introduced. Signed-off-by: Satya Benson <satya@benson.earth>
Signed-off-by: Satya Benson <satya@benson.earth>
Signed-off-by: Satya Benson <satya@benson.earth>
satchlj
force-pushed
the
pr/j613-sep-26-6-2-policy
branch
from
November 3, 2026 18:55
499838b to
c50ca33
Compare
Author
|
Fixed ABI 3 expectations in c50ca33; all three sensor diagnostic tests pass on Linux. The commit checker requires a carrier sign-off on carried commits. Rebased the existing series to sign 069366d in place (now 8ed1f3f), with no duplicate prerequisite, and pushed with an explicit force-with-lease against the old head. All four commits pass the trailer checker; the inherited prerequisite content is unchanged. Written by Claude on @satchlj's behalf. |
satchlj
marked this pull request as ready for review
November 3, 2026 22:25
satchlj
requested review from
chriskearney,
maralcbr and
scottjones
as code owners
November 3, 2026 22:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keep the existing T8122 transport and v4 biometric interface. On J613 OS firmware 26.6.2, require the boot-forwarded identity and xART guard for writable attachment and fail closed on host-store/index errors. Add default-on trusted_keys/filevault_api options so existing-bag deployments can omit those APIs. Add read-only cached policy diagnostics without UUIDs, keys or enclave operations.
Depends on #234. The carried prerequisite is already under review there; review only the J613 policy and diagnostic commits here, and drop the prerequisite after #234 merges. The original policy delta was owner-verified on a composed C13 kernel for positive/negative fingerprint verification, password fallback, lock/unlock, cold reboot and daily-root return. Production-boundary tests pass normally and with Python -O; the exact firmware predicate passes a native Rust test. The added diagnostic path passes a modules-only LLVM/Rust build with BTF generation and split-BTF decoding against completed C13 kernel interfaces. Full branch CI passes. On 2026-11-03 a C13k kernel carrying these commits booted on a J613 MacBook Air with 26.6.2 firmware. The diagnostic readback reported status=verified with identity_source=dt and no mismatches. Lock-screen unlock with the enrolled finger worked, an unenrolled finger was rejected, and sudo with the fingerprint worked. That machine now runs this kernel as its daily system. No new provisioning, storage format or firmware protocol is introduced.