Skip to content

fix(ssh): trust ~/.ssh/known_hosts too (v0.16.3) - #72

Merged
ralyodio merged 1 commit into
mainfrom
fix/hashed-known-hosts
Oct 19, 2026
Merged

ralyodio merged 1 commit into
mainfrom
fix/hashed-known-hosts

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Fixes #71. SshSession read only DiskPush's own known_hosts, so fleet run, ls, the TUI and desktop treated every host OpenSSH already trusts as unknown. It now also reads ~/.ssh/known_hosts read-only (new trustedKnownHostsPaths option, default that file; hashed entries were already supported). Newly accepted keys still go to DiskPush's own file.

Verified: with an empty DISKPUSH_HOME and no --accept-new, fleet run --on dev2,dev3,devchovy,bbs-root succeeds on all 4 (it failed on all 4 before). pnpm test: 933/934; the one failure is the live rsync permissions test, which needs umask 022 (this box is 007). Bumps to 0.16.3.

🤖 Generated with Claude Code

…t 'unknown' (v0.16.3)

SshSession only read DiskPush's own known_hosts, so `diskpush fleet run` called every
server OpenSSH already trusted 'not in known_hosts' unless --accept-new was passed.
It now also reads ~/.ssh/known_hosts (hashed entries included) read-only; newly
trusted keys are still written to DiskPush's own file. Fixes #71.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ralyodio
ralyodio merged commit 3116e1e into main Oct 19, 2026
6 checks passed
@ralyodio
ralyodio deleted the fix/hashed-known-hosts branch October 19, 2026 15:23
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.

fleet: hosts in a hashed ~/.ssh/known_hosts are reported as 'not in known_hosts'

1 participant