Skip to content

Conversation

@TravisEz13
Copy link
Member

No description provided.

@TravisEz13 TravisEz13 added the Compliance Related to compliance requirements label Nov 15, 2017
@TravisEz13 TravisEz13 added this to the 6.0.0-RC milestone Nov 15, 2017
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why we don't add this in all csproj files via PowerShell.Common.props?

Copy link
Collaborator

@iSazonov iSazonov left a comment

Choose a reason for hiding this comment

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

LGTM.

One minor question. Sometimes msbuild is a surprise. How we can check that the option really works?

@TravisEz13
Copy link
Member Author

We will run binskim during the official build which will tell us.
https://github.com/Microsoft/binskim

@daxian-dbw
Copy link
Member

daxian-dbw commented Nov 15, 2017

We don't build pwsh.exe, so is the executable also has this option set on?
According to https://msdn.microsoft.com/en-us/library/jj835761.aspx, if not, powershell may not be able to benefit from this option.

This is not a blocking comment.

@iSazonov
Copy link
Collaborator

Copy link
Member

@daxian-dbw daxian-dbw left a comment

Choose a reason for hiding this comment

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

LGTM. :shipit:

@daxian-dbw daxian-dbw merged commit 5d8999e into PowerShell:master Nov 15, 2017
@TravisEz13 TravisEz13 deleted the add_HighEntropyVA branch November 15, 2017 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Compliance Related to compliance requirements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants