Skip to content

Fix credential scan issues - #4927

Merged
Travis Plunk (TravisEz13) merged 2 commits into
PowerShell:masterfrom
TravisEz13:FixCredentialScanIssues
Sep 27, 2017
Merged

Travis Plunk (TravisEz13) merged 2 commits into
PowerShell:masterfrom
TravisEz13:FixCredentialScanIssues

Conversation

@TravisEz13

@TravisEz13 Travis Plunk (TravisEz13) commented Sep 26, 2017 •

Copy link
Copy Markdown
Member

Add suppression for lines with secrets.
Add suppressions for files which are secrets.
This will be consumed in the VSTS daily build.

Renamed tests with ConvertTo-SecureString to avoid false positives

@SteveL-MSFT Steve Lee (SteveL-MSFT) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -1,8 +1,9 @@
Describe "ConvertTo-SecureString" -Tags "CI" {
Describe "ConvertTo--SecureString" -Tags "CI" {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to have an extra - between ConvertTo and SecureString

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have to rename it to something other than convertto-securestring.

Describe "ConvertTo--SecureString" -Tags "CI" {

Context "Checking return types of ConvertTo-SecureString" {
Context "Checking return types of ConvertTo--SecureString" {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to have an extra - between ConvertTo and SecureString

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the previous comment

@megamorf

Copy link
Copy Markdown
Contributor

Just out of curiosity, is the CS002:SecretInNextLine suppression VSTS specific? Haven't seen that before.

@TravisEz13

Travis Plunk (TravisEz13) commented Oct 17, 2017 •

Copy link
Copy Markdown
Member Author

Sebastian N. (@megamorf) It's specific to the tool we use. Unfortunately, the tool itself is internal to Microsoft only. That is why we run it in VSTS and not our normal CI systems.

@megamorf

Copy link
Copy Markdown
Contributor

Travis Plunk (@TravisEz13) Ah, that makes sense. Thanks for the answer :-)

Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj-contribs/PowerShell that referenced this pull request Aug 6, 2026
* Add file secret suppression
* Add line secret suppression
* This will be consumed in the VSTS daily build.
* Renamed tests with ConvertTo-SecureString to avoid false positives
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants