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.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Reply via email to