Cairn
NousResearch/hermes-agent

Restrict config.yaml file permissions to 0600

Cluster 59726 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These issues and PRs address config.yaml remaining world-writable through write paths that bypass permission enforcement, with fixes proposed to cap file mode at 0600 in atomic write operations.

Open issues1

  • Issue#59726config.yaml can stay world-writable indefinitely through ~10 write paths that bypass save_config()'s final chmod

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: duplicate 1 · other 2

  • #59727 security(utils): cap config.yaml mode to 0600 in atomic_yaml_write · other → df714ad
  • #59740 fix(utils): cap config.yaml mode at 0600 in atomic_yaml_write · other → #59727
  • #60818 fix(config): secure direct YAML writes · duplicate → #59727, #59726
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
hermes cli
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/59726.json
cluster/59726.md