Check for mark-of-the-web
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 a security precaution, dsc should probably check for mark-of-the-web for:
- configurations
- resource manifests
- executables used by a resource
Proposed technical implementation details (optional)
Should probably require the user to remove the mark and not have a switch to override it.
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 tracing DSC's handling of configurations, resource manifests, and executables used by resources. Determine how mark-of-the-web is detected and define the rejection behavior for each case, including the proposed no-override policy. The issue names no files, entry points, or tests; done means marked inputs are consistently blocked.
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
- Needs clarification
- Newbie friendliness
- 35/100