Simulate tech port unlock #8994
Open
Conversation
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
plotnick
force-pushed
the
tech-port-unlock
branch
9 times, most recently
from
eda7430 to
f0e2398
Compare
Depends on management-gateway-service commit c80fb4f23108691dea43239b55a14f5e47f161b7.
plotnick
force-pushed
the
tech-port-unlock
branch
from
f0e2398 to
d22110b
Compare
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.
Depends on oxidecomputer/management-gateway-service#434, supports oxidecomputer/permission-slip#252. Does not actually unlock anything, but implements the server side of the challenge/response protocol of RFD 492, including ECDSA signature validation.
sp-simloads its trusted keys fromsmf/switch_zone_setup/support_authorized_keysat startup (by default; seesp-sim/examples/config.toml). We don't compile them into the binary like Hubris does.