Cairn
NousResearch/hermes-agent

Secure hermes backup file permissions and location

Cluster 59735 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 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 the hermes backup defaulting to an insecure location and lacking restrictive file permissions, with fixes to set chmod 0600 on the backup zip and default its path under HERMES_HOME.

Open issues1

  • Issue#59735hermes backup defaults to $HOME with no chmod -- doesn't inherit ~/.hermes's 0700 protection

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: other 2

  • #59736 security(backup): default hermes backup under HERMES_HOME, chmod 0600 · other
  • #59738 fix(hermes_cli): chmod 0600 on hermes backup zip · other → #59736
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.67: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/59735.json
cluster/59735.md