PowerShell / PowerShell/PSScriptAnalyzer
Issue with AvoidUsingPlainTextForPassword
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
I am setting a parameter $Credential but its being flagged to force the use of secure string, However I don't belive that I am doing something 'insecure'
Example:
Param(
[Parameter()]
[System.Management.Automation.CredentialAttribute()]$Credential
)
I don't think above code should trigger a warning that it could expose sensitive information unless i am mistaken.
Thanks,
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 reproducing the example with the AvoidUsingPlainTextForPassword rule and inspect that rule's implementation and existing tests. Determine whether a CredentialAttribute parameter should trigger the diagnostic, then add or update coverage so the intended warning behavior is explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devtools, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100