kyber | s2n | |
---|---|---|
6 | 9 | |
689 | 4,450 | |
2.2% | 0.2% | |
5.1 | 9.5 | |
4 months ago | about 11 hours 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.
kyber
-
Quantum Computers Break Encryption in China But Far From Cracking Bitcoin
I wouldn’t even be worried about the banks, any mode of encryption used for data would be at stake, but there’s already some algos that are quantum secure made by Crystal Kyber. Here’s their git repo: https://github.com/pq-crystals/kyber.git
-
NSA, NIST, and post-quantum cryptography
So, question then, isn't one of the differences between this time's selection, compared to previous selections, that some of the algorithms are open source with their code available.
For example, Kyber, one of the finalists, is here: https://github.com/pq-crystals/kyber
And where it's not open source, I believe in the first round submissions, everyone included reference implementations.
Does the code being available make it easy to verify whether there are some shady/shenanigans going on, even without NIST's cooperation?
-
NIST Announces First Four Quantum-Resistant Cryptographic Algorithms
The C reference code is available: https://github.com/pq-crystals/kyber
- NIST announces PQC-algoritms to be standardized
- Kyber key encapsulation mechanism (Post Quantum Cryptography Standardization)
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?
minisign - A dead simple tool to sign files and verify digital signatures.
OpenSSL - TLS/SSL and crypto library
openssl - Fork of OpenSSL 1.1.1 that includes prototype quantum-resistant algorithms and ciphersuites based on liboqs [OQS-OpenSSL 1.1.1 is NO LONGER SUPPORTED, please switch to OQS-Provider for OpenSSL 3]
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.
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.
Selenite - An Experimental Rust Crate for Post-Quantum Code-Signing Certificates.
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.
libsodium - A modern, portable, easy to use crypto library.
falcon
Botan - Cryptography Toolkit