Relationships
↔ sibling #4768#4764 @swamp/ssh: a model that calls a fleet can't tell how that fleet checks host keys
Opened by randybias · 11/15/2026· Shipped 11/15/2026
Type: feature request.
Versions: @swamp/ssh 2026.10.23.1, swamp 20261114.210101.0.
What happens: @swamp/ssh lets each fleet member choose how its host key is checked (hostKeyPolicy: pinned,
tofu, accept-new or insecure). A model that drives the fleet through context.runModel cannot find out which
one applies to a host:
resolvereturns each matched host's name, address, port, user, tags, attributes and transport kind, but not its host-key policy;- the
hostrecords written byapplycarry the same fields, again without the policy; - a model cannot read another definition's arguments, so it cannot look the policy up there either.
What we expected: resolve's hosts and the host records also report each host's effective host-key policy.
That is the policy the connection will actually use: pinned when only host keys are given. When no policy applies,
the field is left out.
Shortest reproduction:
- Define an
@swamp/sshfleet with two hosts, one withhostKeyPolicy: pinned(and itshostKeys), one withhostKeyPolicy: insecure. - From another model, call the fleet's
resolvewithallthroughcontext.runModel, then read theselectionrecord it wrote. - The two hosts look the same: nothing in the record tells them apart.
Why it matters: a model that makes a dangerous change over the fleet can't refuse a host whose identity isn't checked. A firewall change that must not lock the operator out is one example: it should run only against a host whose key is pinned. Today such a model has to trust whatever the fleet is set to, or ask the caller to restate the policy by hand, and a restated value proves nothing.
Upstream repository: https://github.com/swamp-club/swamp-extensions
Environment
- Extension:
@swamp/ssh@2026.10.23.1 - swamp:
20261114.210101.0-sha.537e03d1 - OS:
linux(x86_64) - Deno:
2.9.8 - Shell:
/bin/bash
Shipped
Click a lifecycle step above to view its details.
system commented 11/15/2026, 12:47:25 AM
Classified automatically when this issue was filed.
- Source: Extensions
If you feel this classification is incorrect, add a ripple to tell us so.
stack72 commented 11/15/2026, 10:39:40 PM
Thanks @randybias for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.
Sign in to post a ripple.