osslsigncode | OpenSSL based Authenticode signing for PE/MSI/Java CAB files | SSH Utils library

by mtrojnar C Version: 2.5 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | osslsigncode Summary

osslsigncode is a C library typically used in Utilities, SSH Utils applications. osslsigncode has no bugs, it has no vulnerabilities and it has low support. However osslsigncode has a Non-SPDX License. You can download it from GitHub.

osslsigncode is a small tool that implements part of the functionality of the Microsoft tool signtool.exe - more exactly the Authenticode signing and timestamping. But osslsigncode is based on OpenSSL and cURL, and thus should be able to compile on most platforms where these exist.

Support

Quality

Security

License

Reuse

Support

osslsigncode has a low active ecosystem.

It has 478 star(s) with 109 fork(s). There are 11 watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 102 have been closed. On average issues are closed in 84 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of osslsigncode is 2.5

Quality

osslsigncode has no bugs reported.

Security

osslsigncode has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

osslsigncode has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

osslsigncode releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of osslsigncode

Get all kandi verified functions for this library.

osslsigncode Key Features

No Key Features are available at this moment for osslsigncode.

osslsigncode Examples and Code Snippets

No Code Snippets are available at this moment for osslsigncode.

Community Discussions

Trending Discussions on osslsigncode

Problem with ENGINE_load_private_key and PKCS#11

Using which command in NodeJS

How to signing digital signature for macos app bundle and linux executable

Code Signing with a Certum certificate

QUESTION

Problem with ENGINE_load_private_key and PKCS#11

Asked 2019-Jul-22 at 12:37

Being stuck with signing (Authenticode) using PKCS#11 tokens, and given the amazingly poor driver support from the vendor (SafeNet), we're signing Windows code on Linux.

All of this is working fine using all of our tokens on several build servers. However, I have one token that fails, depending on the mechanism being used. From Java, using Jsign and the SunPKCS11 provider, everything works fine with this token.

However, from osslsigncode, signing fails with this token:

...

ANSWER

Answered 2019-Jul-22 at 12:37

The solution, at least for now, seems to be just deleting the CA certs from the token (via SAC Tools on Windows). Once done, osslsigncode (via the PKCS#11 stack) has no problem finding the token. The CA certs aren't needed for signing, so deleting them presents no problem.

Source https://stackoverflow.com/questions/56860252

QUESTION

Using which command in NodeJS

Asked 2019-Jun-19 at 14:29

I'm currently working on porting a CoffeeScript to native NodeJS but I'm coming across a few bumps, It's basically "signing" after injecting files.

The error I'm getting is: ReferenceError: which is not defined

Here's my Node code:

...

ANSWER

Answered 2019-Jun-19 at 14:29

I presume the application you were using this with was using the which package to verify whether a binary exists.

You'd need to install this and call it using the Node syntax.

Source https://stackoverflow.com/questions/56669976

QUESTION

How to signing digital signature for macos app bundle and linux executable

Asked 2018-Nov-29 at 14:08

I have an java swing application and building executable for three platform Window (exe), macOS(.app) an linux(.sh). I also have a .p12 file and need to signed for three platform executable.

I have signed for exe file on windows by osslsigncode and can check as digital signature tab in properties of exe file.

Now, I facing with problem that is i don't know how to sign a .p12 file to macOS executable(.app) and linux executable(.sh).

I also confuse that can we sign the .p12 file to macOS and Linux executable on linux build server like windows digital signature?

I have used linux build server to build executable for three platform

I also try with openssl command as:

...

ANSWER

Answered 2018-Nov-29 at 14:08

you can extract the private key form the .p12 (pfx) with this command

Source https://stackoverflow.com/questions/53498397

QUESTION

Code Signing with a Certum certificate

Asked 2017-Jan-05 at 07:21

I want to sign a static .exe build of one of my Open Source programs so that it will be executable in a "normal" manner to a "normal" Windows user.

I bought an Open Source Code Signing Certificate from certum.eu to be able to do this.

After some searching on the internet, I tried to sign the exe file using osslsigncode 1.7.1 on my Linux maching using

...

ANSWER

Answered 2017-Jan-05 at 07:21

Short answer: Wait a couple of days and the problem will disappear.

I had the same issue with my Certum certificate earlier this year. And a few years ago, I had a commercial certificate I got from Comodo and it initially had the same issue as well.

The bottom line is that your new certificate and signed binaries needs some time to gain trust and auto-verified by Microsoft's code-signing reputation service.

Start distributing your signed exe to as many PC as you can and do the "advanced" option to force the exe to run anyway. That might help bump the reputation up faster.

Source https://stackoverflow.com/questions/41474100

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install osslsigncode

You can download it from GitHub.

Support

Check whether your your question or suspected bug was already discussed on https://github.com/mtrojnar/osslsigncode/issues. Otherwise, open a new issue. BUT, if you have questions related to generating spc files, converting between different formats and so on, please spend a few minutes searching on google for your particular problem since many people probably already have had your problem and solved it as well.

Find more information at: