build(key-provider): switch to upstream repo and update deps#533
Merged
build(key-provider): switch to upstream repo and update deps#533
Conversation
Switch from kvinwang fork to upstream MoeMahhouk/gramine-sealing-key-provider (commit 180ff46). The fork was needed for the dcap-qvl 0.3.10 security fix, which has since been merged upstream along with: - Gramine v1.5 -> v1.9 - Rust toolchain -> 1.85 - Hardened attestation flow - Removed sgx.enable_stats Also regenerated Cargo.lock to fix bytes vulnerability (RUSTSEC-2025-0014).
Restore version pinning for git and build-essential matching jammy.
kvinwang
force-pushed
the
fix/key-provider-upstream
branch
from
463d1e0 to
6912f60
Compare
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
1 participant
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.
Summary
bytesvulnerability (RUSTSEC-2025-0014)Test plan
docker compose build gramine-sealing-key-provider