-
Notifications
You must be signed in to change notification settings - Fork 112
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
go/runtime/registry: allow client nodes to run sgx runtimes #4832
Conversation
3468f44
to
29bea1c
Compare
Codecov Report
@@ Coverage Diff @@
## master #4832 +/- ##
==========================================
- Coverage 66.74% 66.61% -0.13%
==========================================
Files 452 452
Lines 50336 50338 +2
==========================================
- Hits 33597 33534 -63
- Misses 12586 12643 +57
- Partials 4153 4161 +8
Continue to review full report at Codecov.
|
29bea1c
to
1a4c2a0
Compare
go/runtime/registry/config.go
Outdated
@@ -37,6 +37,9 @@ const ( | |||
CfgRuntimePaths = "runtime.paths" | |||
// CfgSandboxBinary configures the runtime sandbox binary location. | |||
CfgSandboxBinary = "runtime.sandbox.binary" | |||
// CfgRuntimeEnv sets the runtime environment. Setting an environment that does not |
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.
Looks like something is up with the linter, maybe since the update to Go 1.18?
// CfgRuntimeEnv sets the runtime environment. Setting an environment that does not | |
// CfgRuntimeEnvironment sets the runtime environment. Setting an environment that does not |
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.
Okay, this is totally messed up. I'm going to fix the linter. Sorry for using so much jernej-lint
. Next time won't have issues!
1a4c2a0
to
e5d2e55
Compare
e5d2e55
to
df7c7ce
Compare
This PR allows client nodes to run SGX runtimes, which enables them to request keys from a (privately) peered key manager. The
RuntimeDebugForceELF
flag was replaced with a more general one. The former one doesn't seem to be used in this repo, so it should be okay.