Files supported for signing
The file types outlined in this article are supported for signing via the command line interface (SMCTL).
For signing, we offer traditional tool-based signing and simple signing.
With traditional signing, SMCTL integrates with third-party signing tools and identifies the best tool to sign with. Alternatively you can specify a specific signing tool to sign with.
With simple signing, there are no dependencies on third-party tools, extra libraries, or external signing infrastructure.
To learn more about simple signing, see Sign binary commands.
Files supported for simple signing
注意
Simple signing is a newly introduced feature. We're working to expand its capabilities, including adding supported file types and metadata capturing, as well as troubleshooting raised issues.
Signing method | Supported file type |
|---|---|
Authenticode / SignTool | .arx, .cab, .cpl, .crx, .dbx, .deploy, .dll, .efi, .exe, .msi, .ocx, .ps1, .psm1, .stl, .sys, .xsn, .msix, .appx, .wsf, .js, .deploy |
Jarsigner | .ear, .jar, .sar, .war |
Mage | .application, .manifest, .vsto |
Signtool 32-bit | .doc, .docm, .dot, .dotm, .mpp, .mpt, .pot, .potm, .ppa, .ppam, .pps, .ppsm, .ppt, .pptm, .vdw, .xla, .xlam, .xls, .xlsb, .xlsm, .xlt |
Files supported for traditional signing
To identify the signing tools you require:
Identify the file types you need to sign.
Select the signing tool name associated with the file types you want to sign.
Select the signing tool name in the table to view installation and integration instructions.
Follow the instructions to install the signing tool.
Identify which Software Trust client tool it requires for signing.