Repository navigation
docs(windows): add key-only SSH access to the Windows VM runbook - #47
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4ead5a3d17
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | Access | Value | | ||
| | --- | --- | | ||
| | Remote Desktop | `10.10.50.30` | | ||
| | SSH (PowerShell, key-only) | `ssh -i ~/.ssh/win01 josh@10.10.50.30` | |
There was a problem hiding this comment.
When an operator has several identities loaded in ssh-agent, this command may offer unrelated keys and exhaust the server's authentication attempts even though ~/.ssh/win01 is correct. With OpenSSH 9.6, ssh -G -i <file> reports identitiesonly no; the full command at line 88 already avoids this failure, so add -o IdentitiesOnly=yes to the table command as well.
AGENTS.md reference: AGENTS.md:L30-L34
Useful? React with 👍 / 👎.
| the key, write the new public key to | ||
| `C:\ProgramData\ssh\administrators_authorized_keys` and update the variable | ||
| so a rebuilt VM gets it. |
There was a problem hiding this comment.
When the replacement key is mistyped or its matching private key is unavailable, overwriting the sole entry in administrators_authorized_keys makes every new SSH session fail after the current session closes, while password and keyboard-interactive recovery are explicitly disabled. Keep the old key while adding the replacement, verify a second connection using the new key, and only then remove the old key and update the variable; the runbook should include the concrete commands and expected observation.
AGENTS.md reference: AGENTS.md:L30-L34
Useful? React with 👍 / 👎.
1 participant
Companion to GilmanLab/fleet#33.