Skip to content

docs(soc): make odin's sshd keys only, as alexander's is - #1539

Merged
Gerrrt merged 1 commit into
mainfrom
fix/odin-sshd-keys-only
Nov 16, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
fix/odin-sshd-keys-only

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Nov 16, 2026

Copy link
Copy Markdown
Owner

What changed

build-the-soc-guest.md §2 gains SSH: keys only, the same step alexander's §2 has. It writes /etc/ssh/sshd_config.d/10-homelab.conf with password, keyboard-interactive and root logins off and X11 forwarding off, then proves from Hicks that a password is refused and a key still works. §10 checks it with sshd -T. security.md gains a row for odin's SSH, and the changelog records the change.

The step has not been run on odin. Until it has, odin keeps taking passwords.

Why

The read-only audit of odin on 2026-11-13 found sshd offering publickey,password. With sudo on 2026-11-15, sshd -T read passwordauthentication yes and x11forwarding yes. odin holds the SOC's CA key and its own age key, and its sshd answers all of VLAN 30, with no host firewall. This brings it into line with alexander, garuda, fenrir, gandalf and oracle.

Blast radius

odin's SSH only, and only once the step is run. Every SSH login to odin in its journal since September was by key (114, from five addresses, all as barnabas), so turning passwords off locks no one out. The runbook keeps a session open while the change is made.

  • No change to network segmentation or firewall rules
  • No new port published to a VLAN that could not already reach the service
  • No credential added outside secrets/*.sops.yaml

Verification

python3 scripts/check_docs.py passed. ./scripts/lint.sh passed with 4 checks skipped, because their tools aren't installed on odin: yamllint, ruff (twice) and ansible-lint. The full make validate wasn't run on odin, because it pulls about 24 GB of images onto a 46 GB root disk; CI runs it.

  • make validate passes
  • Deployed to the lab and confirmed working
  • Docs updated (docs/, service README, or docs/roadmap.md)

🤖 Generated with Claude Code

The 2026-11-13 audit of odin found sshd taking passwords and X11
forwarding, and sshd -T on 2026-11-15 confirmed both. build-the-soc-guest.md
§2 now writes 10-homelab.conf, which sorts ahead of cloud-init's drop-in,
with password, keyboard-interactive and root logins off and X11
forwarding off. §10 checks it with sshd -T, and security.md has a row for
it. Every login in odin's journal since the build used a key. Not yet
applied on odin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings November 16, 2026 17:12
@Gerrrt
Gerrrt enabled auto-merge (squash) November 16, 2026 17:13

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for the SSH hardening documentation change.

No open issues 🎉

What changed in this PR

Documents key-only SSH hardening for odin, aligning the SOC guest’s setup with alexander. The procedure has not yet been applied; odin still accepts passwords.

Changes:

  • Adds an SSH configuration drop-in disabling password, keyboard-interactive and root logins, plus X11 forwarding.
  • Adds fresh-connection login probes and an sshd -T verification step.
  • Records the security posture and distinguishes the documentation change from deployment.
File Description
docs/​security.md Describes odin’s SSH exposure and pending hardening.
docs/​runbooks/​build-the-soc-guest.md Adds key-only SSH setup and verification instructions.
docs/​changelog.md Records the new procedure as not yet deployed.

Review effort: Balanced

@Gerrrt
Gerrrt merged commit 3cd179a into main Nov 16, 2026
9 checks passed
@Gerrrt
Gerrrt deleted the fix/odin-sshd-keys-only branch November 16, 2026 17:21
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.

2 participants