This repository was archived by the owner on Aug 3, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 131
fix: keep enclave signing key out of image builds #694
Merged
smtmfft
merged 10 commits into
hotfix/hotfix-based-on-1.16.1
from
fix/enclave-key-secret-build
Jun 25, 2026
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
7059c70
fix: keep enclave signing key out of image builds
smtmfft fa19248
fix: support GCP Secret Manager enclave key
smtmfft 2d01181
chore: update mainnet SGX verifier addresses
smtmfft c424811
chore: update gaiko submodule verifier config
smtmfft 5101d1a
chore: update internal devnet chain spec
smtmfft ebb8675
fix: align devnet SGX verifier addresses
smtmfft f117eb9
fix: restore devnet verifier config
smtmfft af4f7d5
fix: align gaiko embedded chain specs
smtmfft c59a912
fix: remove invalid shasta chain spec forks
smtmfft 5da6773
fix: unblock enclave key CI build
smtmfft File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
This file was deleted.
Oops, something went wrong.
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes
Dockerfilerequire bothENCLAVE_KEY_PUBLIC_SHA256and theenclave_keyBuildKit secret, but the existingdocker/docker-compose*.ymlbuild blocks forDockerfileonly setcontext/dockerfile(and sometimesENABLE_SELF_REGISTER) and never provide that arg or secret. Any documented local flow such asdocker compose build raikowill now fail at this first signing step (and the same requirement is repeated in the runtime stage), even when the user hasdocker/enclave-key.pemlocally, because compose is not passing it as a build secret.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in 5da6773: compose/CI builds no longer require a BuildKit secret because the Dockerfile generates a throwaway RSA-3072/e=3 key only when no secret/hash is supplied. Release builds still pass ENCLAVE_KEY_PUBLIC_SHA256 and fail if the secret is missing.