Cairn

auth.json permissions security fix: owner-only from creation

NousResearch/hermes-agent · cluster 126950 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 2 PRs.

A security issue where auth.json (containing refresh tokens) is created world-readable before permissions are tightened, and a failing chmod can leave it permanently exposed. The associated changes address seeding the file with correct owner-only permissions from the moment of creation.

Open issues1

  • Issue#126950[Security] `auth.json` (refresh tokens) is created world-readable before being tightened, and a failing `chmod` leaves it that way permanently

Open PRs2

  • PR#126957fix(docker): seed auth.json owner-only from the first instant
  • PR#130620fix(tools): write memory files owner-only

1 PR closed without merging

From the close comments: other 1

  • #126967 fix(docker): seed auth.json 0600 from first instant, never abort on chmod · other → #126957, #126950
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/126950.json
cluster/126950.md