Repository navigation
Spinbox Remote 2.1.0: spin ssh-session and this machine's OpenSSH - #11
Merged
Merged
Conversation
2.0.0 connects with ssh2, whose key exchange the workspace's sshd no longer offers from spin-machine v20261113.03 on (spin-machine#245: mlkem768x25519-sha256 alone), and spin main already pins v20261114.02: the next spin release would open no spin+ workspace with 2.0.0. 2.1.0 carries #6 (spin ssh-session and spin tunnel) and #8 (the system OpenSSH, which negotiates ML-KEM). test:e2e passed against spin's e2e stack at f15122137 (spin-machine v20261114.02) with VS Code 1.146.0 (69047191fc42): 8 tests, open, reconnect, stopped, key not enrolled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
2.0.0, the version spin pins, connects with ssh2. From spin-machine v20261113.03 on, the workspace's sshd offers only
mlkem768x25519-sha256(spin-machine#245), and spin main already pins v20261114.02. So the next spin release would leave everyspin+workspace unable to open with 2.0.0.2.1.0 carries #6 (
spin ssh-sessionandspin tunnel) and #8 (this machine's OpenSSH, which negotiates ML-KEM).Verified
go tool task test:e2eagainst spin's e2e stack at spin f15122137 (spin-machine v20261114.02), VS Code 1.146.0 (69047191fc42): 8/8 passed (open, reconnect to the same server, stopped, key not enrolled). This is the lane #8 says was never run on the OpenSSH code.After merge
Tag
v2.1.0(publish.yml), then move thespinbox-remotepin and sha256 in spin's versions.yaml before spin's next release.Part of spin-stack/vscode-spinbox#24.
🤖 Generated with Claude Code