cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-8307) cordova-windows cert expires in 2015
Date Thu, 09 Apr 2015 18:49:12 GMT


ASF GitHub Bot commented on CB-8307:

Github user robpaveza commented on the pull request:
    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,
-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:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message