Introduction
Apache Milagro Crypto C 2.0.1-incubating is the second Apache Software foundation release of this library.
Library Description
milagro-crypto-c is a modern cryptographic C library that focuses on Elliptic Curve Cryptography but has support for legacy systems that require RSA. There is support for three different security levels; 128, 192 and 256 bit. It has been written only in C and has no external dependencies other than an entropy source. Measures have been taken in the code base to prevent side channel attacks. Pairing based cryptography (PBC) is a maturing field that has recently gained widespread acceptance. The library supports schemes that make use of PBC such as BLS for short signatures and MPIN for multi-factor authentication (MFA).
v2.0.1 Release Rationale
There are two main additions to the library and they both impact the API hence the jump from v1.0.0 to v2.0.1:
Shamir's Secret Sharing (SSS) has been added to the library. There is also functionality combining the existing BLS solution with SSS to enable signature aggregation without revealing the secret key share. This change is required by the Milagro DTA (https://github.com/apache/incubator-milagro-dta) and will allow subsequent releases of the DTA to be built from an official Apache release of the crypto-c library.
The Paillier additively homomorphic cryptosystem has also been added which will be required by subsequent releases of the DTA to enable Multi-Party Computation of cryptocurrency wallet addresses and subsequently to create transaction signatures for these wallets.
The library now also supports Python 3 and formulas in the documentation are now rendered using MathJax.
Please see the README for build/test instructions, a list of contributors and guidelines on how to contribute yourself.
Disclaimer
Apache Milagro Crypto C (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.