microsoft / microsoft/winget-cli
Default behavior for dealing with signed or unsigned configuration files by settings
Open
Nobody has claimed this yet.
Area-Settings
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
WinGet should support signed and unsigned configuration files.
There should be additional warnings/errors related to the files when they don't conform to the default behavior.
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
No files, tests, or entry points are named in the issue. Start by locating WinGet's configuration-file handling and any existing signature validation, then clarify the default treatment of signed and unsigned files. Done should include defined behavior plus appropriate warnings or errors for files that do not match it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100