-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(tee-proof-verifier): add backward compatibility logic #245
Closed
pbeza
wants to merge
12
commits into
pab/solidity-compatible-offchain-proof-verifier
from
pab/versioned-backward-compatible-offchain-proof-verifier
Closed
feat(tee-proof-verifier): add backward compatibility logic #245
pbeza
wants to merge
12
commits into
pab/solidity-compatible-offchain-proof-verifier
from
pab/versioned-backward-compatible-offchain-proof-verifier
Conversation
This file contains 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
…action-30.x chore(deps): update cachix/install-nix-action action to v30
pbeza
force-pushed
the
pab/versioned-backward-compatible-offchain-proof-verifier
branch
6 times, most recently
from
January 10, 2025 13:35
dc50556
to
570e45a
Compare
pbeza
force-pushed
the
pab/versioned-backward-compatible-offchain-proof-verifier
branch
from
January 10, 2025 13:44
570e45a
to
7f15706
Compare
Signed-off-by: Harald Hoyer <[email protected]>
fix(teepot-tee-quote-verification-rs): memory leak
Free the FFI collateral on rust checks anyway to prevent memory leaks. Also remove the `TryFrom<&sgx_ql_qve_collateral_t>` as it is unsafe. Signed-off-by: Harald Hoyer <[email protected]>
fix(teepot-tee-quote-verification-rs): free collateral on ffi error
4 tasks
Signed-off-by: Harald Hoyer <[email protected]>
feat(tdx): add nix build for TDX google VMs
Signed-off-by: Harald Hoyer <[email protected]>
feat(tee-key-preexec): add test container for tee-key-preexec
…d-compatible-offchain-proof-verifier
Closing in favor of #251. |
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.
This is the second, more robust version of the TEE proof verifier's backward compatibility logic. It attempts both the new and old verification processes and doesn't rely on explicit
report_data
versioning. An alternative, simpler approach was implemented in #244.