Don't request write permissions for RemotePowerShellConfig.txt#102
Open
Tadas wants to merge 1 commit into
Open
Don't request write permissions for RemotePowerShellConfig.txt#102Tadas wants to merge 1 commit into
Tadas wants to merge 1 commit into
Conversation
5 tasks
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
1 participant
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.
PR Summary
Change remoting config file (
%windir%\System32\PowerShell\7.5.0\RemotePowerShellConfig.txt) reader to use an input stream instead of an input/output stream. This means that write access is no longer needed in this system directory.PR Context
This should help with issues:
MicrosoftDocs/PowerShell-Docs#11682
PowerShell/PowerShell#18741
PowerShell/PowerShell#20180
PowerShell/PowerShell#14274
PowerShell/PowerShell#17367
Tip
For completeness sake, I will mention that if you change
(Get-PSSessionConfiguration -Name <session_config_name>).Filenameto point at the dll that is present in PowerShell's install location (e.g."C:\Program Files\PowerShell\7\pwrshplugin.dll") it should work without write permissions, with the added benefit of always having this file auto-updated when a new version of PowerShell is installed.Excellent write up in https://awakecoding.com/posts/enable-powershell-winrm-remoting-in-powershell-7/ shows the command to do that: