minisign
s2n
minisign | s2n | |
---|---|---|
12 | 9 | |
1,967 | 4,450 | |
- | 0.2% | |
4.8 | 9.5 | |
about 1 month ago | 1 day ago | |
C | C | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
minisign
- Ask HN: What are your favorite tiny, single purpose tools?
- Minisign A dead simple tool to sign files and verify signatures
-
PGP signatures on PyPI: worse than useless
There are alternatives, minisign and signify.
-
Can a program be the only thing able to have access to a private key?
You don't have to attach identities to public and private keys. If all you need it for is signing, then check out minisign.
-
How should I encrypt files for sharing over the internet?
If you need signatures, minisign is a similar hard-to-misuse program.
-
Beginner: how to do basic cryptography for a blog
In your case, use a tool such as https://jedisct1.github.io/minisign/ to do signing/verification. GPG is another choice which is very common. It will produce a "signature" which can be embedded alongside your posts verifying that the text of the post was endorsed by someone bearing the given public key.
-
Is it worth it to make the move to ProtonMail & VPN?
Claiming it's not ancient because Linux desktop distributions still use it for signing packages is a very odd argument. Most Cryptography experts (note: I'm not talking about programmers, IT professionals or people who know a thing or two about cryptography, I mean actual cryptographers) would agree that we should start using something like signify or minisign instead of the bloated mess that is GPG for signing package repositories.
-
Hacker News top posts: Dec 23, 2021
minisign\ (5 comments)
- minisign
- Show HN: Pagesign – A Python Wrapper for Age and Minisign
s2n
-
S2n-TLS – A C99 implementation of the TLS/SSL protocol
It seems to support multiple options but requires you pick at least one of them. https://github.com/aws/s2n-tls/blob/main/docs/BUILD.md#build...
-
OpenSSL 1.1.1 End of Life
I think GnuTLS is probably the second most popular TLS library, after openssl.
I'll also mentions s2n and rustls-ffi for completeness as C libraries, though the former isn't widely used, and the latter is very experimental still. https://github.com/aws/s2n-tls and https://github.com/rustls/rustls-ffi respectively.
-
I want XAES-256-GCM/11
I've seen operating on unauthenticated plaintext enough times to list it as my own pet peeve with AES-GCM. But it's a problem for chunked messages too. A few years ago we released a SCRAM mode that makes very minimal changes to AES-GCM so that it mathematically can't operate on unauthenticated plaintext. https://github.com/aws/s2n-tls/tree/main/scram
-
Golang is evil on shitty networks
> The documentation is kind of vague, but apparently you have to re-enable it regularly.[3]
This is correct. And in the end it means more or less that setting the socket option is more of a way of sending an explicit ACK from userspace than a real setting.
It's not great for common use-cases, because making userspace care about ACKs will obviously degrade efficiency (more syscalls).
However it can make sense for some use-cases. E.g. I saw the s2n TLS library using QUICKACK to avoid the TLS handshake being stuck [1]. Maybe also worthwhile to be set in some specific RPC scenarios where the server might not immediately send a response on receiving the request, and where the client could send additional frames (e.g. gRPC client side streaming, or in pipelined HTTP requests if the server would really process those in parallel and not just let them sit in socket buffers).
[1] https://github.com/aws/s2n-tls/blob/46c47a71e637cabc312ce843...
-
S2n-QUIC (Rust implementation of QUIC)
It looks like by default s2n-quic uses this TLS implementation, which is not based on the ring crate (though it is written in C)
https://github.com/aws/s2n-tls
-
LibreSSL Languishes on Linux
I would be interested in the other SSL implementations:
- https://github.com/awslabs/s2n
- https://boringssl.googlesource.com/boringssl
- https://bearssl.org/
Are these subpar implementations or there are other reasons not to use these?
What are some alternatives?
signify - OpenBSD tool to sign and verify signatures on files. Portable version.
OpenSSL - TLS/SSL and crypto library
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
mbedTLS - An open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API. Releases are on a varying cadence, typically around 3 - 6 months between releases.
age-plugin-yubikey - YubiKey plugin for age
LibTomCrypt - LibTomCrypt is a fairly comprehensive, modular and portable cryptographic toolkit that provides developers with a vast array of well known published block ciphers, one-way hash functions, chaining modes, pseudo-random number generators, public key cryptography and a plethora of other routines.
ed25519 - Minimal ed25519 Haskell package, binding to the ref10 SUPERCOP implementation.
LibreSSL - LibreSSL Portable itself. This includes the build scaffold and compatibility layer that builds portable LibreSSL from the OpenBSD source code. Pull requests or patches sent to [email protected] are welcome.
kyber
libsodium - A modern, portable, easy to use crypto library.
mkp224o - vanity address generator for tor onion v3 (ed25519) hidden services
Botan - Cryptography Toolkit