What Authenticode/SignTool File Types are Supported by PKI Proxy?
PKI Proxy can add Authenticode signatures to any of the executable file types listed below.
| File Types | ||||
|---|---|---|---|---|
| .appx | .cpl | .efi | .msm | .sys |
| .appxbundle | .crx | .exe | .msp | .vbs |
| .arx | .dbx | .js | .ocx | .vsix |
| .cab | .deploy | .msi | .psi | .vxd |
| .cat | .dll | .msix | .psm1 | .wsf |
| .cbx | .drx | .msixbundle | .stl | .xap |
| .xsn | ||||
Authenticode signatures use Microsoft's proprietary format for signing executable files, which normally requires having a certificate or key locally installed. By configuring PKI Proxy as a Key Storage Provider (KSP), remote certificates and keys become available as if they were local.
For complete details on how PKI Proxy securely accesses certificates and keys for Authenticode signatures, please refer to the Getting Started guide or the documentation.
We appreciate your feedback. If you have any questions, comments, or suggestions about this article please contact our support team at kb@nsoftware.com.