PowerShell / PowerShell/PowerShell-RFC
Idea: Is there a need for having ExecutionPolicy for PS7 and WinPS be mirrored?
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 467
- Forks
- 140
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Summary of the new feature / enhancement
I am wondering if users find it frustrating to have to change the execution policy on both Windows PowerShell and PowerShell 7 separately? Like would folks prefer if it were changed in PS 7 it also changes it in WinPS? or vice a versa? or does it not matter much since you may use one predominately and the other does not matter as much.
Interested to hear folks thoughts. In my head it seems this change could lead to security issues but unsure of specifics. Or is this overall just a ludicrous idea 😅
Proposed technical implementation details (optional)
Have ExecutionPolicy of Windows PowerShell 5.1 follow whatever the ExecutionPolicy of PowerShell 7.x
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reviewing how ExecutionPolicy is stored and evaluated in Windows PowerShell 5.1 and PowerShell 7.x, then document the security implications and define whether changes should mirror in both directions and what behavior would count as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100