vmssh: the CA set is only blamed when the row proves it #118
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/vmssh-refusal"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
[claude 2026-09-02] handshakeError now takes the delegating CA's fingerprint (read off the offered certificate) and the VM's frozen trusted_cas (threaded through vmLookup). The mismatch message is claimed only when the set is known, readable whole, and excludes the delegating CA; otherwise the refusal says the set does include it (or that nothing here can compare) and names the four guest-side causes — trust file/drop-in overwritten (agents older than v0.0.8 with BYO write_files), clock outside the cert window, principal mismatch — and points at the console. Eight vmssh tests plus one boot lookup test.
Migrated from git-collab patche
3497ecbd3bcf2ed748d09b0f7285cb1044d9c5b5.Original author: a73x dev@a73x.sh.
Fixes #115
Revision 1:
82e03a851104ed960ec28ee3f6054e6cc4904de2; base81b4b6c1ca2b07794222ef7cd452e02d7dec46b4