Hermes home directory permissions and symlink security
Cluster 111299. Data as of
Nothing open on GitHub. Fix merged in #111450 on 15 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111450. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111450. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address securing the HERMES_HOME directory to mode 0700 when an ancestor path (not the directory itself) is a symlink, a scenario common on macOS where /tmp and /var are symlinks. A related native test failure on macOS involving Hermes home permissions is also included.
Open issues0
Open PRs0
Fixes on record
-
#111450 fix(security): HERMES_HOME under a symlinked parent (macOS /tmp, /var) is secured to 0700 (#111299, salvage #111301)
files:
hermes_cli/config_home.py,tests/hermes_cli/test_home_directory_diagnostics.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#111301 fix(security): secure HERMES_HOME when only an ancestor path is a symlink · done elsewhere →
56d2438,2e320e6
Closed issues · 1
- Closed#111299Native test failures on macOS: relay traceparent and Hermes-home permissions
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.00means 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 LabAt a glance
- Merged PRs
- #111450
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026