Thales Maciel 617008e8f1 config: normalize ssh_key_path — expand ~/, reject non-absolute ... Bug: resolveSSHKeyPath returned a configured ssh_key_path verbatim. That meant: - ssh_key_path = "~/.ssh/id_ed25519" kept the literal "~" — downstream readers (internal/guest/ssh.go, internal/daemon/image_seed.go, internal/daemon/vm_authsync.go, internal/cli/ssh.go) do raw os.ReadFile on the path and fail at runtime with a path that looks fine but isn't. - ssh_key_path = "id_ed25519" (relative) silently worked or didn't depending on the daemon's cwd — the daemon process's cwd is not the user's shell cwd, so behavior was non-obvious. Fix: add normalizeSSHKeyPath() run over configured values. It: - expands "~/..." against $HOME - rejects bare "~" (ambiguous) - rejects "~user/..." (we don't do user-tilde) - rejects relative paths outright - returns filepath.Clean'd absolute paths Tests cover the accepting case (home-anchored expansion) and every rejection branch via a table-driven subtests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-22 17:00:34 -03:00
..
config.go	config: normalize ssh_key_path — expand ~/, reject non-absolute	2026-04-22 17:00:34 -03:00
config_test.go	config: normalize ssh_key_path — expand ~/, reject non-absolute	2026-04-22 17:00:34 -03:00