CIRCL
secp256k1-voi
CIRCL | secp256k1-voi | |
---|---|---|
6 | 1 | |
1,182 | 27 | |
1.9% | - | |
8.0 | 8.3 | |
7 days ago | 7 months ago | |
Go | Go | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
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.
CIRCL
-
Lattice Asymetric Encryption
- https://github.com/cloudflare/circl
- Circl: Cloudflare Interoperable Reusable Cryptographic Library
-
Is the reference implementation of Classic McEliece in the NIST submission the only good source available for developers out there? General post-quantum questions.
I'm not sure if portability, speed, or general security is on require level here, but Cloudflare's CIRCL library is working on adding support for McEliece, you can find the implementation PR at https://github.com/cloudflare/circl/pull/378
- NIST post-quantum picks Kyber and Dilithium in Go
- NIST announces PQC-algoritms to be standardized
-
Hertzbleed Attack
The attack in question was only tested on SIKE, so it seems logical to start targeted disclosure on the community using and developing it, while using the general disclosures to target the broader cryptographic community.
Both Cloudflare and Microsoft are one of the few companies that have put significant investments into developing SIKE for post-quantum cryptography. Microsoft has a SIKE research team, and Cloudflare has been exploring SIKE for post-quantum TLS for years.
Both companies also maintain the key open-source implementations of SIKE [1][2], and Microsoft is spearheading the effort to standardize SIKE through NIST. Most open source cryptographic libraries don't implement SIKE.
[1]: https://github.com/cloudflare/circl
secp256k1-voi
-
A Dive into the Math Behind Bitcoin Schnorr Signatures
I was searching for implementations to get a more concrete idea of the algorithm and came across https://github.com/Yawning/secp256k1-voi which appears to be well commented, robust, and often also entertaining. There’s also a musig2 one by the same author.
What are some alternatives?
kyber
mathcord - Discord Math Bot using Custom-Made Shunting Yard (WIP), Custom-Made SHA-512, Custom-Made ED25519
liboqs-go - Go bindings for liboqs
noble-secp256k1 - Fastest 4KB JS implementation of secp256k1 signatures and ECDH
yubisigner - YubiSigner provides a convenient way to sign and securely verify file signatures with Yubico YubiKey, utilizing an organization's PKI infrastructure.
memguard - Secure software enclave for storage of sensitive information in memory.
falcon.py - A python implementation of the signature scheme Falcon
multi-party-sig - Implementation of protocols for threshold signatures
curve25519-voi - High-performance Curve25519/ristretto255 for Go.
bips - Bitcoin Improvement Proposals
PQCrypto-SIKE - This software is part of "Supersingular Isogeny Key Encapsulation", a submission to the NIST Post-Quantum Standardization project.
sigtool - Ed25519 signing, verification and encryption, decryption for arbitary files; like OpenBSD signifiy but with more functionality and written in Golang - only easier and simpler