CA5393 warning results from allowing less secure dll locations
Open
Nobody has claimed this yet.
bug
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 124
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
I had to disable CA5393 to avoid warnings in the generated CsWin32 sources. Since that rule is built into the SDK, I wonder if it would be reasonable for CsWin32 to suppress that rule automatically on relevant methods?
Originally posted by @alexrp in https://github.com/microsoft/CsWin32/issues/617#issuecomment-1279761103
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 with the CA5393 documentation and inspect how CsWin32 generates the affected P/Invoke methods and diagnostics. Determine which generated methods are relevant, then verify that the completed change prevents CA5393 warnings without requiring consumers to disable the rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100