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

go/registry/api: Fix node registration when TEE not available #5177

Merged
merged 1 commit into from
Feb 10, 2023

Conversation

peternose
Copy link
Contributor

No description provided.

@kostko kostko added the c:breaking/consensus Category: breaking consensus changes label Feb 10, 2023
@peternose peternose added the c:registry Category: entity/node/runtime registry service label Feb 10, 2023
@peternose peternose enabled auto-merge February 10, 2023 12:35
Previously, registration skipped the TEE hardware verification if a node
registered without TEE capability.
@peternose peternose force-pushed the peternose/fix/registration-with-nil-tee branch from 51521a8 to fc4068c Compare February 10, 2023 14:16
@peternose peternose disabled auto-merge February 10, 2023 14:16
@peternose peternose enabled auto-merge February 10, 2023 14:41
@peternose peternose merged commit b6c2073 into master Feb 10, 2023
@peternose peternose deleted the peternose/fix/registration-with-nil-tee branch February 10, 2023 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:breaking/consensus Category: breaking consensus changes c:registry Category: entity/node/runtime registry service
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants