Need new ArgKind to inform importers and adapters to check content is signed
Open
Nobody has claimed this yet.
Issue-Enhancement
Needs Triage
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
As part of the authenticode scenario, once we have settings to handle signing of content (whether it's a warning or error), we need a way to inform importers and adapters to check their own content.
Proposed technical implementation details (optional)
Define a new ArgKind:
{
"untrustedContent": "[error|warn]"
}
DSC itself would either error or warn if the importer or adapter doesn't use this ArgKind.
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
Locate the ArgKind definition and the importer and adapter entry points, then read how DSC currently handles warnings or errors from them. Add the untrustedContent ArgKind with error and warn behavior, and verify that DSC reports the configured outcome when an importer or adapter does not use it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100