Disallowed cloaked PFX binaries in external packages#4803
Disallowed cloaked PFX binaries in external packages#4803ellahathaway merged 2 commits intodotnet:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the source-build binary allowlist to stop permitting certain PFX (certificate) binaries that are present in external package sources, aligning with the goal of disallowing “cloaked” PFX binaries during source-build prep.
Changes:
- Removed the allowlist entry for Humanizer test PFX files under
src/source-build-reference-packages. - Removed the allowlist entry for Azure IdentityModel test certificate PFX files under
src/source-build-reference-packages.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Merging this PR is contingent on the binaries being cloaked from the VMR. Otherwise, the VMR tests fail continue to fail with new detected binaries: |
|
The PFX files were removed with https://github.com/dotnet/dotnet/pull/4609/changes and the pattern seems correct for those: Do we know why they showed up again with 4c474d7#diff-88c628c55921c35a7fcaee849f15bbb6a7cad031f421b2aeb8e40d1fb4007aef We'll fix the Spectre pattern. |
|
Adding the no-merge label until we cloak the offending binaries. |
|
Will merge once #4914 goes in |
|
@ellahathaway I've merged the dependent PR - #4914 |
Related to dotnet/source-build#5480