[Code Signing Certificate]: MimeKit

[jstedfast]

Project Name

MimeKit

Onboarding Checklist

• Register trade name @ChrisSfanos
• Create configuration in Code Signing Service
• Create organization with DigiCert
• Request certificate from DigiCert
• Received certificate and finalize sign service configuration

[jstedfast]

Question: It just occurred to me that I might need a second code signing certificate for MailKit? I'm not sure if they should use the same certificate or not (I am a complete noob when it comes to code signing).

While MimeKit and MailKit are technically separate projects, they are very closely related. I'm not sure what the recommendation would be.

[glennawatson]

So the signing certificate will say the project name along with dotnet foundation. Then for the actual signing process it'll be locked to the GitHub account or DevOps account.

So it depends if you want the signing certificate to say Mailkit and mimekit in the name.

From a logistics point of view easier on us most likely just to use the one for both projects

[jstedfast]

I'd be fine with the certificate saying MimeKit

[ChrisSfanos]

I've registered MIMEKIT with the WA DOR

[elachlan]

Any progress on this?

[ChrisSfanos]

Hey @elachlan - I created the organization entry in DigiCert - they have a validation process and it's slow. I just pinged them for an update

[elachlan]

@ChrisSfanos sorry to pester you. Has there been any updates from DigiCert?

[jstedfast]

Just a friendly ping. Hoping to see this progress towards completion.

[ChrisSfanos]

Hey @jstedfast and @elachlan - let me get back to this today/tomorrow - sorry for the delays

[elachlan]

Hi @ChrisSfanos, did you manage to get a status update?

[ChrisSfanos]

@elachlan - I did (I was out at MVP Summit all last week) - we were able to get the CSR over to Digicert today so I expect the cert back this week. Future ones will be same day on request (the validation of a new 'entry' in the DNF requires a bunch of hoops unfortunately