ShutterTEE MS1+2: block verificaiton#693
Open
DragonDev1906 wants to merge 9 commits intoshutter-network:mainfrom
Open
ShutterTEE MS1+2: block verificaiton#693DragonDev1906 wants to merge 9 commits intoshutter-network:mainfrom
DragonDev1906 wants to merge 9 commits intoshutter-network:mainfrom
Conversation
This prevents secret keys from being stored in plain text, if running in a TEE.
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
2 participants
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 PR contains the changes needed to run a Shutter Keyper in SGX (including the previous PR):
For details see rolling-shutter/tee/README.md
Security of Keypers running in SGX can be further improved by only processing verified events. The TEE-based light client has support for this (see rolling-shutter/tee/cmd/demo.go). Integrating this requires replacing or changing all syncers and reading events from a channel instead of asking a potentially untrusted Go-Ethereum (push vs fetch).