Add FileExtensionSignInfo for .cab to fix unsigned cab files inside ANCM MSIs#66443
Conversation
There was a problem hiding this comment.
Pull request overview
Adds signing configuration so .cab cabinet archives produced/embedded by ANCM MSI builds are code-signed, addressing signing compliance failures for unsigned CAB payloads.
Changes:
- Add a
FileExtensionSignInfoentry to sign.cabfiles using theMicrosoft400certificate. - Document the intent in
eng/Signing.propsnear existing signing exclusions.
| <!-- Sign cabinet archives embedded inside MSI installers (ANCM, hosting bundle, etc.) --> | ||
| <FileExtensionSignInfo Include=".cab" CertificateName="Microsoft400" /> |
There was a problem hiding this comment.
The new .cab signing rule is inside the ItemGroup labeled "Code sign exclusions", which now mixes exclusions (CertificateName="None") with a positive signing rule. Consider moving the .cab entry to a separate ItemGroup (or updating the label) to keep the intent clear for future edits.
There was a problem hiding this comment.
Good catch - moved the .cab entry into its own ItemGroup (Label=Container signing) above the exclusions group. This keeps the intent clear: exclusions are None, container signing rules are separate.
e6d8b33 to
c22892a
Compare
3d8c2ee to
4e17ba2
Compare
a1ec329 to
1be622d
Compare
Add FileExtensionSignInfo for .cat so catalog files covering customer-modifiable JS templates are signed with Microsoft400. Update .js exclusion comment to clarify: JS files are excluded from Authenticode because they are customer-modifiable templates, covered by catalog signing instead. VS signing compliance bugs: 2951246, 2991694
1be622d to
d2458f8
Compare
\ CertificateName=\Microsoft400\ />
\\
Affected payloads
Precedent
Same fix pattern applied in other dotnet repos:
Tracking