6 Commits

Include renames

Author	SHA1	Message	Date
beatzaplentyandClaude Sonnet 4.6	9e34b9cbb9	fix(push-host-keys): detect non-interactive stdin, direct to SUDO_PASS ... read exits non-zero when stdin is not a terminal (set -e killed the script silently). Catch that and emit a clear error pointing to the SUDO_PASS environment variable rather than crashing with no output. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-07-25 15:55:50 +10:00
beatzaplentyandClaude Sonnet 4.6	2743d664a5	fix(push-host-keys): remove /dev/tty probe, plain read is sufficient ... /dev/tty exists as a device node even without a controlling terminal, so -r/-w tests pass but opening it fails. Plain 'read -r -s' from stdin is enough: works interactively from a real terminal, and from a non-tty context the caller should set SUDO_PASS in the environment instead. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-07-25 15:53:00 +10:00
beatzaplentyandClaude Sonnet 4.6	cfa34f3565	fix(push-host-keys): fall back to stdin when /dev/tty unavailable ... Environments without a controlling terminal (containers, CI agents) don't have /dev/tty. Try it first for the sudo password prompt, fall back to plain stdin so the script works in both contexts. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-07-25 15:51:04 +10:00
beatzaplentyandClaude Sonnet 4.6	e021b49412	fix(push-host-keys): prompt sudo password once, pass via sudo -S ... Instead of ssh -t (requires PTY on both sides), prompt for the sudo password once at startup and pipe it to each remote invocation via sudo -S. This works from any context -- interactive terminal, background agent, or script -- with no PTY needed on either end. Also accepts SUDO_PASS from the environment for non-interactive callers. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-07-25 15:49:27 +10:00
beatzaplentyandClaude Sonnet 4.6	0c29c6a93d	fix(push-host-keys): fix sudo PTY allocation failure ... ssh -t won't allocate a PTY when its own stdin is redirected (by a heredoc). Replaced the heredoc-fed 'sudo bash -s' with commands passed as an argument string so stdin stays free and -t can properly allocate a PTY for the sudo password prompt. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-07-25 15:39:06 +10:00
beatzaplentyandClaude Sonnet 4.6	d74efd9f66	feat(secrets): add push-host-keys.sh; integrate into sync/recover scripts ... New script: scripts/secrets/push-host-keys.sh - Pushes newly-generated SSH host keys from host-keys/ to already-running NixOS hosts after sync-host-keys.sh --regenerate-all-keys. - Before pushing any key, checks that .sops.yaml and secrets/*.yaml are committed and pushed to the remote Gitea flake (hosts rebuild from there, so recipient changes must land first); offers to auto-commit/push if not. - Reads /etc/flake-target from each host to confirm which key to install, handling the case where multiple flake targets share a hostname. - Deduplicates by hostname in --all mode; skips hand-registered targets that have no host-keys/ entry. - --dry-run, --skip-git-check, SSH_USER override (default: nixos). sync-host-keys.sh --regenerate-all-keys: - Updated pre-confirmation warning to distinguish already-running hosts (need push-host-keys.sh) from not-yet-deployed hosts (need installer image rebuild). - Added next-steps block after regeneration completes pointing to push-host-keys.sh --all. recover-hosts.sh: - Header and SSH host key mismatch warn now cross-reference push-host-keys.sh as the proactive (pre-drift) alternative. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-07-25 15:29:16 +10:00