Downloads:

1,123

Downloads of v 0.8.0:

350

Last Update:

2/3/2018

Package Maintainer(s):

Software Author(s):

  • Frank Denis

Tags:

minisign sign verify signatures libsodium pgp gpg

minisign

0.8.0 | Updated: 2/3/2018

Downloads:

1,123

Downloads of v 0.8.0:

350

Maintainer(s):

Software Author(s):

  • Frank Denis

minisign 0.8.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install minisign, run the following command from the command line or from PowerShell:

>

To upgrade minisign, run the following command from the command line or from PowerShell:

>

To uninstall minisign, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade minisign -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade minisign -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure minisign installed
  win_chocolatey:
    name: minisign
    state: present
    version: 0.8.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'minisign' do
  action    :install
  version  '0.8.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: minisign,
    Version: 0.8.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller minisign
{
   Name     = 'minisign'
   Ensure   = 'Present'
   Version  = '0.8.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'minisign':
  provider => 'chocolatey',
  ensure   => '0.8.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install minisign version="0.8.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator flcdrg on 9/5/2019.

Description

Minisign is a dead simple tool to sign files and verify signatures.

It is portable, lightweight, and uses the highly secure Ed25519 public-key signature system.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$packageName = 'minisign'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = 'https://github.com/jedisct1/minisign/releases/download/0.8/minisign-win32.zip'

Install-ChocolateyZipPackage $packageName $url $toolsDir

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
minisign 0.7.0 361 Tuesday, August 2, 2016 Approved
minisign 0.6.0 235 Saturday, November 28, 2015 Approved
minisign 0.4.0 177 Monday, August 17, 2015 Approved

+Version 0.8.0:
- Multiple files can now be signed at once.
- Support for HaikuOS was added.

+Version 0.7.0:
- The default location of the secret key was changed to ~/.minisign/minisign.key.
- Generating a new set of keys (-G) doesn't replace an existing key pair any more; the additional -f switch is required in order to force this operation.
- Improved error messages and Windows compatibility.
- A man page was added.

+Version 0.6.0:
- Support for pre-hashing (HashEdDSA) was added.
- The -H command-line switch, in addition to -S, enables HashEdDSA signatures instead of the default, pure EdDSA signatures.

HashEdDSA signatures:
- Require very little memory to be generated and verified, even with huge files
- Are faster to generate and verify than pure EdDSA signatures
- Require Minisign >= 0.6. In particular, they are not compatible with OpenBSD signify tool.
- Would not remain secure against (improbable) collisions in the Blake2b-512 hash function.

PureEdDSA signatures (default):
- Require as much memory as the size of the file to sign
- Cannot be used with files whose size is over 1 Gb
- Are compatible with all Minisign versions, as well as OpenBSD signify.
- Would remain secure against (improbable) collisions in the Blake2b-512 hash function.

+Version 0.5.0:
- The return code is now 1 on verification/password error, and 2 for system errors.
- Bug fix: -p and -V could not be used together. It has been fixed.
- New option: -o, that can be combined with -V in order to send the content of the signed file to stdout after successful verification.

+Version 0.4.0:
- New switch: -Q, to display only the trusted comment (after verification)


This package has no dependencies.

Discussion for the minisign Package

Ground Rules:

  • This discussion is only about minisign and the minisign package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or minisign, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus