Forum Discussion

TIMOTHY_MANGAN's avatar
TIMOTHY_MANGAN
MVP
Aug 03, 2018

MSIX Packageing Tool / signtool certificate issues

1) I have a valid (paid for) code signing certificate from a well known CA that has a password so I can't use the in tool signing (which is something you should support!).   The 17134 SDK is presen...
TIMOTHY_MANGAN's avatar
TIMOTHY_MANGAN
MVP
Feb 16, 2021

Mo_Velayati I am using signtool.exe from the windows SDK from a script directly.

 

Attached image is an example of the identity portion of a manifest I recently signed, and another of the subject field as seen in the certificate manager (NOTE: certmgr doesn't display it in the correct form as in the cert file, but you can see the order).

 

Commas were not actually my issue, including the complete certificate subject in the Publisher field was. 

The reference schema (ManifestTypes) for the manifest file is what imposes restrictions on what what is allowed in the Publisher field, and that is where the requirement that it start with CN= comes from.  SignTool is what imposes the matching between this publisher field and the subject field of the cert.

 

 

GrahamGB's avatar
GrahamGB
Iron Contributor
Oct 20, 2024
TIMOTHY_MANGAN, the script you are referring to, is that the same as in the msix toolkit to change certs and publisher information? I recently opened a thread related to this but not sure if itd the same script you had issued with.