* Add opt-in SSH credential proxying
* fix(sshproxy): drop sshpiper fork, authorize only verified keys
Rebuild the SSH listener on stock golang.org/x/crypto/ssh:
- authorization, secret fetch, and upstream login run in
VerifiedPublicKeyCallback, after the client proves key possession
- typed default-deny channel/request policy; refusals no longer drop
the connection
- auth decisions and session requests emit the shared JSON/OTEL audit
entries (mode ssh) with rejected_by and grant annotations
- upstream dials use the proxy-wide upstream_deny_cidrs guard
* fix(sshproxy): interrupt upstream SSH handshake on cancellation
ssh.NewClientConn ignores context, so shutdown or revocation during the
upstream login waited for the handshake deadline.
* test(sshproxy): port SSH proxy tests from #298
Adapt the stacked test suite to the stock x/crypto implementation:
exec/SFTP, revocation, wstunnel v11 and TLS identity, keepalives under
load, handshake deadlines and cancellation, grant validation, and config
loading. Packet-hook policy tests are replaced by a typed policy table.
Co-authored-by: Jonathan Goodwin <jonathan.goodwin@klaviyo.com>
* fix(sshproxy): satisfy errcheck on Close calls
* fix(sshproxy): detect dead peers, relay EOF, classify authorizer outages
- probe both peers with keepalive@openssh.com and end the session after
three silent intervals, so a dropped client cannot hold upstream open
- relay upstream EOF once stdout and stderr drain, before channel close
- treat only 401/403 from the authorizer as denials; other statuses are
audited as errors
- drain upstream requests when the downstream channel accept fails
---------
Co-authored-by: Jonathan Goodwin <jonathan.goodwin@klaviyo.com>
Every secrets transform, credential source, and config reload builds its
own source registry, and each registry had its own 1Password client cache.
The 1Password SDK loads its Wasm core lazily without synchronization, so
concurrent first fetches from different registries each compiled a separate
copy of the core (~150 MB RSS apiece). Twenty requests needing three
1Password-backed secrets peaked at ~470 MB.
Use a single process-wide client cache so SDK client creation is serialized
and the core is loaded once.