5d56a1d902
Terminal connections can now reference a jumpHostIntegrationId on the SSH integration config; the backend connects to the jump host first and tunnels to the real target via ssh2's forwardOut(), rather than connecting directly. Added an ssh_host_keys table and a hostVerifier callback that accepts and stores a host's fingerprint on first connect, then hard-rejects on any mismatch on subsequent connects (trust-on-first-use). Settings previously only ever showed/edited one integration per type, which silently prevented configuring more than one SSH host at all. Added a dedicated multi-host SSH section (per-host Save/Test/Delete, Add SSH Host, and a Jump Host dropdown) so jump-host chaining is actually usable from the UI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BbJV5nm8KPVH1oNJYKpnoF |
||
|---|---|---|
| .. | ||
| src | ||
| .env.example | ||
| Dockerfile | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||