Codesign Application with osslsigncode utility based on a .pfx or .p12 certificate
npm install grunt-osslsigncode> Codesign Application with osslsigncode utility based on a .pfx or .p12 certificate
~0.4.0If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
``shell`
npm install grunt-osslsigncode --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
`js`
grunt.loadNpmTasks( 'grunt-osslsigncode' );
This plugin also requires you to have openssl and osslsigncode installed on your machine. You can install it with this command:
#### Mac OSX
`shell`
brew install openssl
brew install osslsigncode
#### Linux
`shell`
sudo apt-get install openssl
sudo apt-get install osslsigncode
When first running the task you should be prompted to enter the password for your certificate.
The plugin generates a .key and .spc file to a temporary directory that should be excluded from version control.
When running again it detects that the files have already been generated and won't ask you for a password for future releases.
task like so:
`js
grunt.initConfig( {
osslsigncode: {
your_target: {
options: {
// Task-specific options go here.
certificate: 'path/to/certificate.pfx', // path to your .pfx or .p12 certificate
certificateOutput: 'path/to/tmp/output_', // prefix to a temporary output directory for generated certificates
sign: 'path/to/app.exe', // path to your executable that should be signed
output: 'path/to/signed.app.exe', // (optional) path to your signed exe
password: 'your_password', // (optional) certificate password
timestamp: 'http://timestamp.globalsign.com/scripts/timestamp.dll', // (optional) url where timestamp should be fetched from
name: 'App Name', // (optional) your app's name
url: 'http://www.example.com' // (optional) author's url of app
}
},
},
} )
`$3
#### options.certificate
Type:
Default value: A string value that determines the location of the certificate file that is used to sign the application.
#### options.certificateOutput
Type:
Default value: A string that defines a temporary output directory for generated .key and .spc files. Highly recommended to exclude those files from version control.
For example:
js
options: {
certificateOutput: 'store/gen_'
}
`Generates the following files:
store/gen_output.key
store/gen_output.spc
store/gen_tmp_cert.pem
store/gen_tmp_key.pem
#### options.sign
Type:
Default value:
RequiredA string that defines the path to the application's executable that should be signed. (.exe, .msi, etc.)
Task will throw an error if the option is not set.
#### options.output
Type:
Default value:
OptionalAn optional string that defines the output of the signed executable file. If not set overwrites the original executable file defined in
.#### options.password
Type:
String
Default value:
OptionalAn optional string that defines the password stored inside the certificate. If defined no password prompt is shown while generating .key and .spc files.
#### options.timestamp
Type:
Default value:
OptionalAn optional string that defines the a url where the timestamp for signing the application should be fetched from.
#### options.name
Type:
Default value:
OptionalAn optional string that defines the app's name.
#### options.url
Type:
Default value: An optional string that defines the author's url of the app.