Unable to sign windows package, expecting curl 3 during signing
See original GitHub issue- Version:
Latest version (released 8 days ago)
- Target:
Win 32 & 64 bit
- Result
• signing file=dist-electron/win-ia32-unpacked/zzz.exe certificateFile=/project/csc/zzz.p12
Error: Exit code: 1. Command failed: /root/.cache/electron-builder/winCodeSign/winCodeSign-2.4.0/linux/osslsigncode -in /project/dist-electron/win-ia32-unpacked/zzz.exe -out /project/dist-electron/win-ia32-unpacked/zzz-signed-sha1.exe -t http://timestamp.globalsign.com/scripts/timstamp.dll -pkcs12 /project/csc/zzz.p12 -h sha1 -n zzz -i https://zzz.com -pass 5311cc5ff28a74734044ef7574141f9b772beab6605d31a289e53691cc83cd01 (sha256 hash) /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /root/.cache/electron-builder/winCodeSign/winCodeSign-2.4.0/linux/osslsigncode)
/root/.cache/electron-builder/winCodeSign/winCodeSign-2.4.0/linux/osslsigncode: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /root/.cache/electron-builder/winCodeSign/winCodeSign-2.4.0/linux/osslsigncode)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7
Top Results From Across the Web
Known issues and troubleshooting with SignTool - MSIX
This article describes known issues and troubleshooting tips for Sign Tool.
Read more >Self-signed certificates or custom Certification Authorities
If running GitLab Runner as a Windows service, this will not work. Specify a custom certificate file instead. Notes: If your GitLab server...
Read more >Unable to resolve "unable to get local issuer certificate" using ...
I have the self signed certificate installed in the Trusted Root Certification Authorities of my Windows 7 - client machine. I can browse...
Read more >FAQ -- Frequently Asked Questions - curl
3.12 Why do FTP-specific features over HTTP proxy fail? ... certificate that was signed by one of the authorities in the bundle. curl...
Read more >curl_setopt - Manual - PHP
From curl 7.28.1 to 7.65.3 CURLE_BAD_FUNCTION_ARGUMENT is returned. From curl 7.66.0 ... Then set a path to it in your php.ini file, e.g....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The osslsigncode binary is compiled with xenial. The docker image is using bionic. The libraries don’t match.
In electron-builder/winCodeSign/winCodeSign-2.5.0/linux: Changing the Dockerfile’s buildpack-deps to bionic-curl doesn’t work, because the osslsigncode doesn’t work with openssl 1.1.0 which bionic packages. Xenial packages 1.0.0.
If you change: libcurl4-openssl-dev
to libcurl4-gnutls-dev
And run the build.sh, it compiles a binary that works for me.
now the problem appearing again. how should i do?