Skip to content

Fix Gate13 Windows shell and exact SSH key selection - #41

Merged
flujo-app merged 5 commits into
betafrom
codex/gate13-shell-contract
Oct 9, 2026
Merged

flujo-app merged 5 commits into
betafrom
codex/gate13-shell-contract

Conversation

@flujo-app

Copy link
Copy Markdown
Owner

Gate 13 sent commands through Windows OpenSSH's cmd.exe while disabling normal PowerShell profiles. Use an encoded PowerShell adapter, preserve profiles in qualification children, and bind SSH/SCP to one selected private key whose derived public identity and optional fingerprint are checked before installation. Startup refreshes exact keys and verifies SID-based ACLs even after a ready-marker restart. The configuration pin now points to the repaired startup source.

Local qualification: 88 provider, startup, host-job and launcher tests passed, including native cmd.exe/PowerShell execution, actual temporary ssh-keygen identities and Windows ACL replacement. Black 22.3.0, isort 5.10.1 and diff checks passed. One unchanged route-wheel test requires an unavailable pinned artifact and was excluded explicitly. No GCE/IAP machines were contacted; this does not claim a fresh cloud acceptance run.

Targets beta, which owns this harness. Addresses mario-andreschak/FLUJO#494.

@flujo-app
flujo-app merged commit 0a34e99 into beta Oct 9, 2026
0 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant