[
https://issues.apache.org/jira/browse/CB-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487951#comment-14487951
]
ASF GitHub Bot commented on CB-8307:
------------------------------------
Github user robpaveza commented on the pull request:
https://github.com/apache/cordova-windows/pull/65#issuecomment-91325392
I've updated the certificate with a new EKU. That was my bad for not
verifying build with it.
For future reference (in 24.5 years when someone is digging through the
history to get the correct commands...), the tools to generate the valid PFX
for this are in the Windows SDK. The correct usage is:
makecert -r -n "CN=Apache Cordova Team" -a sha256 -cy end -sky signature
-eku 1.3.6.1.5.5.7.3.3,1.3.6.1.4.1.311.10.3.13 -sv CordovaApp_TemporaryKey.pvk
CordovaApp_TemporaryKey.cer
pvk2pfx -pvk CordovaApp_TemporaryKey.pvk -spc CordovaApp_TemporaryKey.cer
-pfx CordovaApp_TemporaryKey.pfx
The makecert parameters are documented on MSDN, but it comes down to
self-signed, end-entity, signing, and the EKU parameters which I missed during
the first commit (I thought makecert added that via the -sky signature
parameter). The EKU is for Code Signing and Lifetime Signing.
> cordova-windows cert expires in 2015
> ------------------------------------
>
> Key: CB-8307
> URL: https://issues.apache.org/jira/browse/CB-8307
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
> Affects Versions: 3.5.0, 4.1.3
> Reporter: Kirk Shoop
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> There is a pfx file checked into the project template that is used to deploy
> the appx to a device when debugging.
> The pfx file contains a certificate that will expire one year after it was
> created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
