Skip to content
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

Compute runtime's key manager should be checked #2459

Closed
kostko opened this issue Dec 9, 2019 · 0 comments
Closed

Compute runtime's key manager should be checked #2459

kostko opened this issue Dec 9, 2019 · 0 comments
Labels
c:registry Category: entity/node/runtime registry service

Comments

@kostko
Copy link
Member

kostko commented Dec 9, 2019

Currently no stateful checks are performed on the registered compute runtime's key manager ID (the only check is that the runtime itself is not also the key manager). Checks are however performed for the genesis document state.

Checks should be added to the RegisterRuntime handler that in case a key manager runtime ID is specified, it must exist and be a valid key manager runtime.

We should also allow explicitly specifying a NULL key manager (e.g., for non-confidential runtimes). (Already part of #2340.)

@kostko kostko added the c:registry Category: entity/node/runtime registry service label Dec 9, 2019
@matevz matevz closed this as completed Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:registry Category: entity/node/runtime registry service
Projects
None yet
Development

No branches or pull requests

2 participants