-
mike S
- PowerBuilder
- Sunday, 27 April 2025 04:53 PM UTC
Has anyone tried this yet? I'm planning to try this after my current cert expires.
FYI - New azure code signing service that includes the certification and HSM for 10/month. Typical EV certs cost well over 200+ year.
Works with signtool as well as anything else you would want to use.
**This applies to powerserver apps as well.
Set up signing integrations to use Trusted Signing | Microsoft Learn
From the Microsoft AI:
To use Trusted Signing with SignTool in Azure, follow these steps:
-
Prerequisites:
- Ensure you have a Trusted Signing account, identity validation, and certificate profile.
- Assign the Trusted Signing Certificate Profile Signer role to an individual or group.
- Use Windows 10 Version 1809/October 2018 Update or newer, Windows 11 (all versions), or Windows Server 2016 or newer.
- Install the Trusted Signing Client Tools.
-
Install SignTool:
- Download and install the Windows SDK SignTool.exe (minimum version: 10.0.2261.755).
- Install the .NET 8 Runtime.
- Download and install the Trusted Signing dlib package.
-
Create a JSON file:
- Create a new JSON file (e.g., metadata.json).
- Add the specific values for your Trusted Signing account and certificate profile to the JSON file. Example:
{ "Endpoint": "<Trusted Signing account endpoint>", "CodeSigningAccountName": "<Trusted Signing account name>", "CertificateProfileName": "<Certificate profile name>", "CorrelationId": "<Optional CorrelationId value>" }
-
Invoke SignTool to sign a file:
- Note the locations of your SDK Build Tools, the extracted Azure.CodeSigning.Dlib, and your metadata.json file.
- Replace the placeholders in the following command with the specific values:
& "<Path to SDK bin folder>\x64\signtool.exe" sign /v /debug /fd SHA256 /tr "http://timestamp.acs.microsoft.com" /td SHA256 /dlib "<Path to Trusted Signing dlib bin folder>\x64\Azure.CodeSigning.Dlib.dll" /dmdf "<Path to metadata file>\metadata.json" <File to sign>
Ensure that you use the recommended Windows SDK version in the dependencies listed, as the dlib file won’t work otherwise. Trusted Signing certificates have a three-day validity, so time stamping is critical for continued successful validation of a signature beyond that period 1.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.