microsoft / microsoft/winget-cli
Support signed configuration files
Open
Nobody has claimed this yet.
Command-Configure
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
PowerShell scripts can be signed, and WinGet configuration files should also be able to be signed.
We should follow the same mechanism as PowerShell scripts.
Then we should look at:
- #4078
- #4079
- #4080
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 by examining how PowerShell scripts are signed and read the related issues #4078, #4079, and #4080. Identify the WinGet configuration-file flow that must follow that mechanism; done means signed configuration files are supported with equivalent signing behavior and verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100