Skip to content

feat(settings): RequireActivationSymlinks for OpenSSH-safe activation links - #39

Merged
coreybutler merged 1 commit into
mainfrom
feat/require-activation-symlinks
Nov 16, 2026
Merged

coreybutler merged 1 commit into
mainfrom
feat/require-activation-symlinks

Conversation

@coreybutler

Copy link
Copy Markdown
Contributor

What

Adds RequireActivationSymlinks (default false) for certified HKLM/GPO so activation links can be forced to symlinks.

Why

Windows OpenSSH Redirection Guard blocks non-admin junctions on PATH (nvm#1564). Symlinks avoid that mitigation while keeping PATH → .nodejs.

Testing

Setting is consumed by cli Link() / ensureActivationLink (follow-up PR).

Risk

Low. Default off; community unchanged unless the value is set manually.

…tion links

Certified HKLM/GPO can require .nodejs activation links as symlinks so
Windows OpenSSH Redirection Guard can traverse PATH (nvm#1564).

Signed-off-by: Corey Butler <770982+coreybutler@users.noreply.github.com>
@coreybutler
coreybutler merged commit 71e0133 into main Nov 16, 2026
2 checks passed
@coreybutler
coreybutler deleted the feat/require-activation-symlinks branch November 16, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant