SSH ControlMaster socket directory path and ownership handling

NousResearch/hermes-agent · cluster 133436 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 3 PRs.

The three members concern where the SSH backend places its ControlMaster Unix socket directory: one reports a "path too long for Unix domain socket" error for named profiles and notes ssh.py does not use socket_safe_tmpdir, one proposes a short per-user root, and one proposes refusing shared-tmp socket dirs not owned by the user. Their status and outcomes are not established by the titles.

Open issues1

  • Issue#133436[Bug]: SSH backend fails with "path too long for Unix domain socket" for named profiles since the scratch TMPDIR change (ssh.py does not use socket_safe_tmpdir)

Open PRs3

  • PR#127863fix(tools): refuse shared-tmp socket dirs we do not own
  • PR#133444fix(ssh): keep the ControlMaster dir inside a short per-user root
  • PR#138978fix(ssh): budget the full ControlMaster listener path for every root
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.