Skip to main content
← Back to list
01Issue
FeatureShippedExtensionsPublicTeam
AssigneesNone

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:

  • resolve returns each matched host's name, address, port, user, tags, attributes and transport kind, but not its host-key policy;
  • the host records written by apply carry 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:

  1. Define an @swamp/ssh fleet with two hosts, one with hostKeyPolicy: pinned (and its hostKeys), one with hostKeyPolicy: insecure.
  2. From another model, call the fleet's resolve with all through context.runModel, then read the selection record it wrote.
  3. 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
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPEDLINKED+ 7 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

11/15/2026, 10:39:35 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 linked sibling of #476811/15/2026, 7:38:50 PM
Editable. Press Enter to edit.

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.