Releases: jedisct1/minisign
Releases · jedisct1/minisign
0.12
- Libsodium is now an optional dependency. When using the Zig toolchain to compile Minisign, you can specify the
-Dwithout-libsodiumflag to build and run without libsodium. - Key identifiers are now zero-padded when printed.
New Contributors
- @ityonemo made their first contribution in #138
- @ryancdotorg made their first contribution in #139
0.11
0.10
- Minisign can be compiled with Zig instead of cmake+make+a C toolchain
- Minimal
VERIFY_ONLYversions can be built again - Prehashing is now enabled by default, regardless of the input size. Support for non-prehashed signatures will eventually be removed
- Legacy signatures can be rejected with the addition of the
-Hflag - Precompiled binaries for Win64, Linux and WebAssembly are now available.
0.9
- New option:
-Rto recover the public key from a secret key. minisigncan now be compiled to WebAssembly.- Error messages have been improved.
- Key derivation is now possible on devices with limited memory.
- Compilation on OpenWRT is now possible using
cmake. - A Docker image is now available.
- 64-bit Windows binaries have been added, and macOS binaries are notarized.
0.8
0.7
- 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-fswitch is required in order to force this operation. - Improved error messages and Windows compatibility.
- A man page was added.
0.6
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
signifytool. - 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.
0.5
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.