Repository navigation
feat(settings): RequireActivationSymlinks for OpenSSH-safe activation links - #39
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.