Downloads:
4,773
Downloads of v 0.8.0:
3,490
Last Update:
03 Feb 2018
Package Maintainer(s):
Software Author(s):
- Frank Denis
Tags:
minisign sign verify signatures libsodium pgp gpg- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
minisign
- 1
- 2
- 3
0.8.0 | Updated: 03 Feb 2018
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
4,773
Downloads of v 0.8.0:
3,490
Maintainer(s):
Software Author(s):
- Frank Denis
minisign 0.8.0
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Frank Denis. The inclusion of Frank Denis trademark(s), if any, upon this webpage is solely to identify Frank Denis goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
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:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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://community.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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download minisign --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade minisign -y --source="'INTERNAL REPO 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="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install minisign
win_chocolatey:
name: minisign
version: '0.8.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'minisign' do
action :install
source 'INTERNAL REPO URL'
version '0.8.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller minisign
{
Name = "minisign"
Version = "0.8.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'minisign':
ensure => '0.8.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. 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 11 Jul 2020.
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.
Log in or click on link to see number of positives.
- minisign.0.8.0.nupkg (c407c4a0c0ee) - ## / 61
- minisign-win32.zip (e74849a99547) - ## / 61
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
minisign 0.8.0 | 3490 | Saturday, February 3, 2018 | Approved | |
minisign 0.7.0 | 536 | Tuesday, August 2, 2016 | Approved | |
minisign 0.6.0 | 395 | Saturday, November 28, 2015 | Approved | |
minisign 0.4.0 | 352 | Monday, August 17, 2015 | Approved |
Copyright (c) 2015 - 2018 Frank Denis
+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.
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.