Tunnel sush through Nexus - #11254
Draft
plotnick wants to merge 1 commit into
Draft
Conversation
This completes the initial integration of the [Support Shell](https://github.com/oxidecomputer/sush) ([RFD 620](https://rfd.shared.oxide.computer/rfd/0620)). We add an unpublished, fleet-admit-only WebSocket endpoint to Nexus that tunnels bytes to a sush proxy in a switch zone. Nexus controls only who may reach the proxy; the platform-ID backed sprockets-TLS, client authn, and job authz inside are untouched. The tunnel is the first WebSocket endpoint that refuses in HTTP before upgrading, so the authz coverage harness gained a method for it. The harness expects privileged requests to fail with 503, because no sush proxy runs in the test environment. The bad-authn probes include the handshake headers, so they reach the authn check and fail with its status. Co-Authored-By: Claude Mythos 5 <noreply@anthropic.com>
plotnick
force-pushed
the
sush-switch-proxy
branch
from
September 6, 2026 23:54
0ce2c9d to
7dc9f6d
Compare
plotnick
force-pushed
the
sush-nexus-tunnel
branch
from
September 6, 2026 23:54
990fb83 to
b6aa684
Compare
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
1 participant
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 completes the initial integration of the Support Shell (RFD 620), building on #11252 and #11253.
We add an unpublished, fleet-admit-only WebSocket endpoint to Nexus that tunnels bytes to a sush proxy in a switch zone. Nexus controls only who may reach the proxy; the platform-ID backed sprockets-TLS, client authn, and job authz inside are untouched.
The tunnel is the first WebSocket endpoint that refuses in HTTP before upgrading, so the authz coverage harness gained a method for it. The harness expects privileged requests to fail with 503, because no sush proxy runs in the test environment. The bad-authn probes include the handshake headers, so they reach the authn check and fail with its status.