#security #verify-signature #ed25519 #openbsd #key #signify

no-std libsignify

Create cryptographic signatures for files and verify them

5 releases

0.6.0 Dec 1, 2023
0.5.3 Jun 4, 2022
0.5.2 Feb 6, 2022
0.5.1 Feb 6, 2022
0.5.0 Feb 6, 2022

#1035 in Cryptography

Download history 13/week @ 2024-02-26 16/week @ 2024-03-04 38/week @ 2024-03-11 19/week @ 2024-04-01 5/week @ 2024-04-08 16/week @ 2024-04-15 5/week @ 2024-04-22 21/week @ 2024-04-29 3/week @ 2024-05-06 4/week @ 2024-05-13 7/week @ 2024-05-20 13/week @ 2024-06-03 51/week @ 2024-06-10

71 downloads per month
Used in signify

MIT license

831 lines

Signify - Ed25519 signature tool

crates.io docs.rs docs License: MIT Build Status

Create cryptographic signatures for files and verify them. This is based on signify, the OpenBSD tool to sign and verify signatures on files. It is based on the Ed25519 public-key signature system by Bernstein et al.

signify-rs is fully compatible with the original implementation. It can verify signatures generated by OpenBSD signify and signs data in a format that it can verify as well.

You can read more about the ideas and concepts behind signify in Securing OpenBSD From Us To You.


cargo install signify


The CLI is designed to be compatible with the reference implementation and accepts the same command line flags as it.

Create a key pair:

signify -G -p pubkey -s seckey

Sign a file using the secret key:

signify -S -s seckey -m README.md

Verify the signature:

signify -V -p pubkey -m README.md

To see how to use libsignify, check out the examples/ directory or the documentation.


There are basic unit tests, but many more are needed for good coverage 😞.

However, we ensure that a full cycle of generating a keypair, then signing & verifying works. To run them, use the following commands:


For correctness, we compare interoperability with the OpenBSD signify:


The complete test suite can be conveniently ran with make test.




~78K SLoC