GPO to control activation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Is your feature request related to a problem? Please describe.
Unable to control WSL activation in a large enterprise. Due to this we cannot manage vulnerabilities/patching etc.
Describe the solution you'd like
A GPO to control if WSL can be activated or not. and/or a way to automate/force upgrades/updates on multiple machines.
Describe alternatives you've considered
Blocking via 3rd party or applocker. Neither is ideal.
Additional context
WSL makes it hard managing security and patching in a global organisation with many who see the shinny toys but have no understanding of the security aspects. It is a very cool product but it seems enterprise control hasn't been considered.
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
The issue names no files, tests, or entry points. Start by reviewing how WSL activation and enterprise policy are currently managed, then clarify whether the scope is a GPO control, automated updates, or both. Done requires an agreed scope and a tested administrative control.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100