Repository navigation
Conversation
This was referenced Oct 26, 2026
zibi-pplx
force-pushed
the
pr958
branch
2 times, most recently
from
October 26, 2026 00:15
114abba to
a05ad68
Compare
This was referenced Oct 26, 2026
This was referenced Oct 26, 2026
zibi-pplx
force-pushed
the
pr958
branch
5 times, most recently
from
October 26, 2026 19:48
c7b9513 to
b2f9daa
Compare
zibi-pplx
force-pushed
the
pr958
branch
3 times, most recently
from
October 26, 2026 23:46
bcce3bd to
4bdf426
Compare
## Summary Let space-ssh reach Windows OpenSSH through the operator-only, execution-fenced node channel. Use the caller's SSH credentials and verified per-sandbox host key, default Windows logins to Administrator, and add user/identity overrides. Skip Linux environment injection for non-Linux guests while retaining the existing Linux path. ## Validation All four CLI tests passed, including credential ownership, host-key checking, fenced proxy selection and identity paths with spaces. Linux-target Clippy passed. Verified both interactive Windows PowerShell and a remote hostname command through space-ssh, and a Linux uname command on an existing sandbox. ## Severity and risk Severity does not apply to this operator feature. Guest OpenSSH and authorized keys must already be provisioned; this does not add a Windows SPACE guest agent. Native guest access requires the preceding node channel and preserves strict host-key verification. ## Stack Windows guests. #954 is a separate reader-guard deployment before #955–#959 enable opaque images. Keep that guard as the rollback floor. #955 supplies the SQLite schema before its readers/writers; deploy the matching supervisor before node/build/template/sandbox managers. Firmware guests remain opt-in, standalone and locally imported; export, pull and cross-node distribution stay refused. AI assistance: Codex implemented the CLI, tests and this description.
This branch has not been deployed
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.
Summary
Let space-ssh reach Windows OpenSSH through the operator-only, execution-fenced node channel. Use the caller's SSH credentials and verified per-sandbox host key, default Windows logins to Administrator, and add user/identity overrides. Skip Linux environment injection for non-Linux guests while retaining the existing Linux path.
Validation
All four CLI tests passed, including credential ownership, host-key checking, fenced proxy selection and identity paths with spaces. Linux-target Clippy passed. Verified both interactive Windows PowerShell and a remote hostname command through space-ssh, and a Linux uname command on an existing sandbox.
Severity and risk
Severity does not apply to this operator feature. Guest OpenSSH and authorized keys must already be provisioned; this does not add a Windows SPACE guest agent. Native guest access requires the preceding node channel and preserves strict host-key verification.
Stack
Windows guests. #954 is a separate reader-guard deployment before #955–#959 enable opaque images. Keep that guard as the rollback floor. #955 supplies the SQLite schema before its readers/writers; deploy the matching supervisor before node/build/template/sandbox managers. Firmware guests remain opt-in, standalone and locally imported; export, pull and cross-node distribution stay refused.
AI assistance: Codex implemented the CLI, tests and this description.
Stack created with Sapling. Best reviewed with ReviewStack.
Base: #924, the separate Cloud Hypervisor installation stack.