发布商身份制作Appx和签名工具 [英] Publisher Identity Make Appx and Signing Tool

问题描述

我们的赛门铁克代码签名证书在我们的证书主题的CN和O中有一个逗号和句点。  我尝试使用\在身份 - >中转义命令。 Publisher属性但它不起作用。  除了使用赛门铁克和
获取没有标点符号的新证书之外，他们可以选择让MakeAppx.exe工具生成带有逗号的CN和O的Appx文件吗？  例如MyComapany，LLC。

Our Symantec code signing certificate has a comma and period in the CN and O of our certificate subject.  I've tried escaping the command with a \, in the Identity -> Publisher attribute but it won't work.  Beside working with Symantec and getting a new certificate with out the punctuation is their an option to get the MakeAppx.exe tool generate an Appx file with a CN and O that has a comma?  E.g MyComapany, LLC.

推荐答案

当我们通过Windows应用商店开发者计划和赛门铁克购买我们的证书时，我们在公司名称中添加逗号。  ;例如。我的公司，LLC。

When we purchased our cert via the Windows Store developer program and Symantec we place a comma in the company name.  E.g. My Company, LLC.

快来了解我们的证书赢了使用makeappx应用程序生成的appx，或者windows store包装XML发布者内容与我们的证书CN和O不匹配。 我无法更改XML，因为它不喜欢额外的逗号

Come to find out our cert won't work with the appx generated using the makeappx application because or windows store packaging XML publisher content does not match our cert CN and O.  I cannot changed the XML because it does not like the extra comma's

我已经提交了一个关于如何在XML中使用逗号来使用makeappx的问题，但我没有回复。 因此，我的下一步是与MS合作，让他们告诉赛门铁克更改我们的证书并删除逗号。 赛门铁克不会做b $ b b因为它是通过windows store开发者程序发布的

I've submitted a question on how to escape the comma's in the XML to work with the makeappx but I've had no response.  So my next step is working with MS to get them to tell Symantec to change our cert and remove the commas.  Symantec won't do it because it was issued via the windows store developer program

这篇关于发布商身份制作Appx和签名工具的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！