{"id":3628,"date":"2023-08-14T13:49:20","date_gmt":"2023-08-14T17:49:20","guid":{"rendered":"https:\/\/www.tmurgent.com\/TmBlog\/?p=3628"},"modified":"2023-08-14T14:21:44","modified_gmt":"2023-08-14T18:21:44","slug":"signing-packages-using-tmeditx-and-digicert-keylocker","status":"publish","type":"post","link":"https:\/\/www.tmurgent.com\/TmBlog\/?p=3628","title":{"rendered":"Signing Packages using TMEditX and DigiCert KeyLocker"},"content":{"rendered":"\n

This article describes support for MSIX Package Signing by TMEditX when using the new DigiCert KeyLocker Code-Signing service.  It will be included in version 3.4 of TMEditX.<\/strong><\/p>\n\n\n\n

Until recently, you had three choices when it came to the signing of your MSIX packages:<\/p>\n

    \n
  1. Create your own free private certificate, suitable when packages are only distributed for consumption inside your own organization.  This produces a password protected PSF file that you use.<\/li>\n
  2. Purchase a code signing certificate from a public Certificate Authority.  This prevents the need to install the certificate on end-user devices and allows for external use of the package (such as for customers or contractors).<\/li>\n
  3. Use Device Guard V2 signing via Azure.  Also free, mainly for use in your Azure tenant.  There are known issues with multiple regions. Here, you never touch the actual certificate.<\/li>\n<\/ol>\n\n\n\n

    Due to problems with large software providers that lost control of their public code signing certificate, the industry is moving to new standards for the storage of the certificates.  DigiCert has an article explaining these new requirements New private key storage requirement for Code Signing certificates (digicert.com)<\/a>  <\/p>\n

    These changes do not affect (at least for now) how you would create\/protect\/use a private code signing certificate, but new certificates from public CAs need to meet the new standards, and Microsoft appears to be closing down Device Guard signing in favor of a new Azure Code Signing service that is currently in private preview mode (GA date is uncertain but I hear that Microsoft has already stopped accepting new Device Guard Certificate service setup requests).<\/p>\n\n\n\n

    It is unfortunate that these new standards will complicate our use of code signing certificates, but we’ll have to live with it.<\/p>\n\n\n\n

    The new standards require that certificates be stored in a secure location; generically we can say this means an HSM device or service.<\/p>\n

    DigiCert started issuing certificates on June 1 that meet the new standards. They offer two choices when buying or renewing your certificate.  You can store on a FIPS 140-2 level 2 compliant HSM based storage (and they will sell you a compliant USB token for $150 or you can use your own), or you can use their KeyLocker cloud-based service (which also has an annual storage fee for the cert that isn’t so well documented at present).<\/p>\n

    To use an HSM device, it needs to be present on the VM where signing is being performed.  This isn’t necessarily convenient for automation or remote VMs.  The use of the KeyLocker service may be automated.<\/p>\n

    To use the KeyLocker service, see the DigiCert documentation for all the details (DigiCert KeyLocker<\/a>), but here is what you’ll do to get set up.<\/p>\n

      \n
    1. You request that your DigiCert account add the KeyLocker Service.  This seems easiest done by purchasing a certificate to be stored there and then adding a note to the technician to add the service to your account.<\/li>\n
    2. Add appropriate user accounts to the KeyLocker service.<\/li>\n
    3. Get the DigiCert ONE API Key.<\/li>\n
    4. Install some DigiCert provided tools on the signing VM. <\/li>\n
    5. Add the path to smctl.exe to the system PATH variable.<\/li>\n
    6. Authenticate with the service and create a client certificate for your device.<\/li>\n
    7. Store the client authentication certificate in the windows certificate store.<\/li>\n
    8. Create a keypair alias on the service that authorizes signing for that key from this device.<\/li>\n
    9. Run “smctl.exe healthcheck” from a command line to prove that you are ready to go.<\/li>\n<\/ol>\n\n\n\n

      To use KeyLocker in TMEditX, you will need to enter some information into the Options page. Normally the page would look something like this:<\/p>\n\n\n\n

      <\/p>\n\n\n\n

      Change the Signing Method to DigiCert Keylocker, type in the keypair-alias and click the button to extract the subject field out of the associated certificate.  This value will be placed in the Subject field below and used to update the Publisher field of the manifest.
      Don’t forget to click the Apply button on the bottom of the page to save these settings!<\/p>\n\n\n\n

      <\/p>\n\n\n\n

      With these settings in place, when you save the MSIX package TMEditX will:<\/p>\n