microsoft / microsoft/winget-cli
Proxy support for non-admin users, under admin supervision
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
IIUC, the --proxy CLI parameter can be enabled by an admin with winget settings --enable ProxyCommandLineOptions, but only for theirselves; this makes it hard to make user-local installs for non-admin users.
While it is indeed advisable to require privilege to choose a proxy to use, it does not weaken security assumptions to allow non-admin accounts to apply the proxy an admin have already configured.
Proposed technical implementation details
No response
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
Start in the WinGet CLI handling for the --proxy parameter and the winget settings --enable ProxyCommandLineOptions setting. Trace how the setting and proxy choice are checked for admin and non-admin users. Done means a non-admin user can apply an administrator-configured proxy without choosing or changing the proxy configuration, with the existing privilege restrictions preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100