Apple attests the app key. Device Passport binds the signing key.
- A App Attest key
- Apple certifies this key for the expected signer app on supported Apple hardware.
- K Signing key
- Device Passport creates this key inside the Secure Enclave for SSH authentication and Git signing.
- D Device key
- The existing key identifies the enrolled device and signs its device-check answers.
Separate device and signing keys let a team require Touch ID for signing while device checks run in the background. Replacing the signing key leaves the device enrollment intact. Apple App Attest on macOS
How the team verifies a key
- The CA sends a single-use challenge. The signer app prepares a record with the challenge, the intended CA, the enrolled device ID, the signing key’s public key, and its declared policy.
- The app binds Apple’s proof to that record. It gives App Attest a SHA-256 hash of the record. The signing key and the enrolled device key each sign the same record.
- The CA verifies the evidence. It checks Apple’s certificate chain, the expected app identity and environment, the challenge and intended CA, and both signatures. The CA saves the enrollment if the declared key policy meets the team’s requirements.
What SSH and Git verify
SSH access
When policy requires the enrolled signing key, the team’s CA checks the device’s posture and issues a short-lived OpenSSH user certificate to that key. The signer app shows a confirmation and uses Touch ID to authorize the authentication signature. The SSH server verifies the team CA’s certificate and the signature from the key named in it. The certificate can carry the CA’s appraisal for audit.
Git commit signing
Git uses the same enrolled signing key with a certificate issued specifically for signing commits. The signer app presents the commit and uses Touch ID to authorize the signature. The Device Passport pull request check can verify the exact signed commit, the CA’s certificate, the repository’s key policy, the enrolled signer’s committer identity, and a matching confirmation receipt. Teams can make the check required through GitHub branch protection.
What a confirmation receipt adds
The signer app can use its App Attest key to sign a receipt that binds the signing key, the operation, and hashes of the payload and confirmation text. The CA verifies the assertion against the stored App Attest public key and requires its counter to advance. A verifier with the signed payload can match it to the receipt.
The receipt records what the app reported about the confirmation. The underlying signature establishes what the Secure Enclave key signed. Touch ID happens locally on the Mac. Apple’s assertion verification guide
Validation status
In testing, a Mac running macOS 27.2.1 produced a production App Attest object that passed the Device Passport verifier. A separate test produced a Secure Enclave–signed Git commit and recorded a matching receipt with a test CA. The Git signing implementation is merged. Full GitHub branch-protection validation remains a separate step. Implementation and validation notes on GitHub (repository access required)