Forum Discussion
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...
Aug 07, 2018
Thanks Bogdan - I'll give that a try.
Aug 07, 2018
Escaping in the dialog box as Bogdan suggested does indeed work.
But the GUI of the tool should just accept the comma and escape it behind the scenes.
In addition, when there is documentation on all of this, the documentation should be clear about what to include in this field. There will be confusion on if OU= parts should be included. Just make it clear in the documentation, especially for people that don't deal in certificates regularly.
- Aug 07, 2018
I spoke too soon...
Entering the escape works to get past the UI dialog and makes a package if you don't sign it. The AppXManifest ends up with the \2C in the publishing field, but then the signtool errors (8007000b) against it. I'm not sure if the fault on that is the PackagingTool or signtool.
I would think that the least confusing solution for everyone is to let the PackagingTool accept the comma (and other escape-worthy characters) and place them in the Publishing field as is, and then fix the signtool to understand and escape if necessary.
Of course the best solution might be to let me point to the certificate earlier in the PackagingTool and have it extract what it needs rather than allow us to mess this all up. Probably still need to fix signtool, but the more of this that can be automated the better.
- Mo_VelayatiJan 28, 2021Copper Contributor
Hi Timothy,
Did you find a solution to this issue?
I'm having the same problem.
Best,
Mo
- Jan 28, 2021
Mo_Velayati I am using a cert without a comma in the ID field. Since I don't have to use my public CA code signing cert to upload to the Microsoft Store, a self-signed cert is OK for internal work.
Eventually, I'll have to solve this if I want to host MSIX package installers on my website, but for now those are just MSIs. So I haven't looked at this to see if it was addressed in the tooling.