Bake the Tilo OS release signer into the runner image #2
Loading…
Reference in a new issue
No description provided.
Delete branch "tilo-release-signer"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a checksum-pinned AWS CLI v2 (2.37.2, AWS-signed archives verified against key FB5DB77FD5C118B80511ADA8A6310ACC4672475C) and the root-owned Tilo OS release signer at
/usr/local/libexec/tilo-release-signer/tilo-release-signer.The signer implements the qos/qos
TILO_PCR_PREDICTION_SIGNERcontract used byos/dev/sign-target-prediction.sh:sign-sha256-rsa-pkcs1:aws kms sign --message-type DIGEST --signing-algorithm RSASSA_PKCS1_V1_5_SHA_256withalias/tilo-pcr-predictionsign-efi: deterministic Authenticode (no timestamp), byte-identical totilo-crypto sign-efi, signed byalias/tilo-efi-signingexport-efi-cert: the Tilo OS release EFI certificate (self-signed through KMS)Credentials come from the job's Forgejo OIDC token (audience
tilo-release-signing) exchanged forTiloForgejoReleaseSignerin a clean environment, the same wayos/dev/configure-cosign-kms.shconfigures Cosign. Key ARNs and public identities are root-owned image files, and every KMS signature is verified against them before it is written.Verified locally: real KMS signatures verify with
tilo-crypto verify-efi/verify-rsa-sha256, repeated EFI signing is byte-identical, and the envelope checkverify-authenticode-envelope.pypasses. The offline test suite runs during the image build.🤖 Generated with Claude Code