Microsoft Trusted Signing service

[Mark- 27]

> Have you set the environment variables AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET?

 

Yes.

 

I do not have the last one "App". Went back over the step #5 instruction (https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/#step-4-create-an-app-registration) and now have a "Trusted Signing Certificate Profile Signer" with "App" as the type.

And drum roll.

 

Submitting digest for signing...

OperationId xxxx: InProgress

Signing completed with status 'Succeeded' in 192.2221622s

Successfully signed: C:\apptest.exe

Number of files successfully Signed: 1
Number of warnings: 0
Number of errors: 0

Thank you very much Fred Ahrens.

Thank you Sudara for your blog post.

[Fred Ahrens 58]

Easy. Isn't it? 

[Mark- 27]

4 minutes ago, Fred Ahrens said:

Easy. Isn't it? 

Indeed.

 

What is the normal time needed for a successful signing? > 1 minute ? more?

[Fred Ahrens 58]

On our systems it takes between 2 to 4 seconds per file. Hard to say what might have an influence on this duration. 

It may depend on the region where your signing account is located. We use West Europe.

Internet speed could also be an important variable in this game.

[Mark- 27]

4 minutes ago, Fred Ahrens said:

On our systems it takes between 2 to 4 seconds per file. Hard to say what might have an influence on this duration. 

It may depend on the region where your signing account is located. We use West Europe.

Internet speed could also be an important variable in this game.

Thanks. Yeah, time of day might have a big impact.