Fix dcap-qvl security vulnerability in key-provider #470
+1,133
−591
Conversation
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
Switch to kvinwang fork with dcap-qvl upgraded from 0.2.0 to 0.3.10. This fixes "Missing Verification for QE Identity" vulnerability. - Update Cargo.lock with dcap-qvl 0.3.10 - Verified release build succeeds Security advisory: GHSA-796p-j2gh-9m2q Upstream PR: MoeMahhouk/gramine-sealing-key-provider#13
kvinwang
force-pushed
the
fix/dcap-qvl-security-v2
branch
from
4a6c3cd to
173a374
Compare
kvinwang
changed the title
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.
Summary
Fix dcap-qvl security vulnerability by switching to a fork with the fix applied.
Security Advisory
Changes
MoeMahhouk/gramine-sealing-key-providertokvinwang/gramine-sealing-key-providerforkRelated
Test plan