From 5ed1cb7aa02fefec051855b9721541fde13a126a Mon Sep 17 00:00:00 2001 From: Chuy Zarate Date: Wed, 25 Mar 2026 17:42:04 -0600 Subject: [PATCH] Add catalog signing for .js files for VS signing compliance The .js files in the Emscripten SDK are customer-modifiable toolchain files that cannot be directly Authenticode-signed (modifying a signed file breaks the signature). Instead, generate a .cat catalog file covering all .js files, which is signed with MicrosoftDotNet500 via the existing FileExtensionSignInfo entry for .cat files. The GenerateCatalogFiles target runs after ReallyBuild on Windows only (makecat.exe is a Windows SDK tool), generates a CDF listing all .js files, produces emscripten-js.cat, and places it in the SDK package directory so it ships alongside the files it covers. This fixes ~14,468 unsigned .js files flagged by VS signing compliance scans. --- eng/Signing.props | 5 ++++- eng/emsdk.proj | 43 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 47 insertions(+), 1 deletion(-) diff --git a/eng/Signing.props b/eng/Signing.props index afc88110f7..3d376905eb 100644 --- a/eng/Signing.props +++ b/eng/Signing.props @@ -8,7 +8,10 @@ - + + + + <_CdfFile>$(ArtifactsObjDir)emscripten-js.cdf + <_CatOutputDir>$(ArtifactsObjDir)upstream\emscripten\ + + + + + + + + +