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.

[Mark- 27]

On 5/31/2024 at 8:57 AM, Mark- said:

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

Just a follow up and a new question.

The time can be a couple of seconds or 191 seconds. When the automated build runs it signs about 20 files. All 20 are 2-4 seconds or all are 191 seconds. Go figure.

 

On another note, I received an email "Action required: Enable multifactor authentication for your tenant by 15 October 2024"

 

We are paying a monthly fee for the code signing service and everywhere I searched the system wants me to sign up for some other "premium" service. I have not found a location to active MFA for the code signing service.

 

Any ideas?

 

[Fred Ahrens 58]

51 minutes ago, Mark- said:

I have not found a location to active MFA for the code signing service.

The e-mail that you received from MS is related to your Azure account, not to code signing. The e-mail should also contain links to the place where you can enable MFA.

[dummzeuch 1462]

3 minutes ago, Fred Ahrens said:

The e-mail should also contain links to the place where you can enable MFA.

Which in itself could be a phishing attempt. Just saying.

[Mark- 27]

19 minutes ago, Fred Ahrens said:

The e-mail that you received from MS is related to your Azure account, not to code signing. The e-mail should also contain links to the place where you can enable MFA.

Yeah that is what I thought but, no links lead to it. Most links lead to documentation.

The one link that gets you to:

 

Selecting Multifactor authentication takes you to:

 

 

"Get Free Premium Trial":

 

Confused.

15 minutes ago, dummzeuch said:

Which in itself could be a phishing attempt. Just saying.

That was might first thought. So I checked it out and it is legit.

 

 

 

[Vincent Parrett 720]

I got the same email and also see the "get a free preimium trial to use this feature" message. Typical Microsoft bait and switch - suck you in with what seems like a low priced offering, only to force another down your throat. So to use azure now in any form, you need to pay AU$9 per user per month just for Entra ID (previously Azure Active Directory). 

[Nigel Thomas 35]

https://azure.microsoft.com/en-us/blog/announcing-mandatory-multi-factor-authentication-for-azure-sign-in/

[Vincent Parrett 720]

Interesting how there is no mention that to use MFA you need to pay for Entra - so they have quietly just raised the cost of entry for Azure.

[Nigel Thomas 35]

My Microsoft account already uses 2FA (Microsoft Authenticator). I've been browsing Azure to see if I need to do anything else, but not found anything yet. Rather hope I'm covered and there are no additional costs. I've not received an email about this yet.