Notices: This section not yet converted to new layout. Download stats are rolling back out.



Package test results are passing.

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

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

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.

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

C:\> choco install minisign

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

C:\> choco upgrade minisign


  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop';
    $packageName = 'minisign'
    $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $url = ''
    Install-ChocolateyZipPackage $packageName $url $toolsDir

Virus Scan Results

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.


This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Frank Denis


Copyright (c) 2015 - 2018 Frank Denis


Release Notes

+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)

Version History

Version Downloads Last updated Status
minisign 0.7.0 347 Tuesday, August 2, 2016 approved
minisign 0.6.0 222 Saturday, November 28, 2015 approved
minisign 0.4.0 159 Monday, August 17, 2015 approved

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 uses cookies to enhance the user experience of the site.