AMCL - Apache Milagro Crypto Library
AMCL is a standards compliant C cryptographic library with no external dependencies.
AMCL is provided in C language but includes a Python wrapper for some modules to aid development work.
NOTE: This product includes software developed at The Apache Software Foundation.
In order to build this library, the following packages are required:
The above packages can be installed in different ways, depending on the Operating System used:
sudo apt-get install -y git cmake build-essential python python-dev python-pip libffi-dev doxygen doxygen-latex parallel sudo pip install cffi
sudo yum groupinstall "Development Tools" "Development Libraries" sudo yum install -y git cmake python libpython-devel python-pip libffi-devel doxygen doxygen-latex parallel sudo pip install cffi
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" brew install cmake brew install pkg-config libffi sudo pip install cffi brew install doxygen brew install parallel
install MinGW Please select the mingw32-base and mingw32-gcc-g++ components. Add C:\MinGW\bin to the PATH variable
install Python. Add *C:\Python27 to the PATH variable
A Makefile is present at the project root that reads the options defined in config.mk. Change these options and then type the following to build and test the library.
The default build (see config.mk) uses multiple curves and RSA security levels. There is an example called testall.c in the examples directory that shows how to write a program to use the different curves etc in a single program. To build and run the example use this script;
NOTE: The default build is for 64 bit machines
git clone https://github.com/milagro-crypto/milagro-crypto-c cd milagro-crypto-c mkdir -p target/build cd target/build cmake ../.. export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:./ make make test make doc sudo make install
On Debian/Ubuntu machine instead of executing the “sudo make install” command it is possible to execute “sudo checkinstall” to build and install a DEB package.
Now you can set the path to where libs and python package are installed:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:./:/opt/amcl/lib export PYTHONPATH=/usr/lib/python2.7/dist-packages
NOTE: The build can be configured by setting flags on the command line, for example:
cmake -DAMCL_CHUNK=64 ../.. cmake -D CMAKE_INSTALL_PREFIX=/opt/amcl -D AMCL_CHUNK=64 -D BUILD_WCC=on ../..
It is possible also to build the library supporting more than one elliptic curve and more than one RSA security level, for example
cmake -DAMCL_CURVE=BN254CX,NIST254 -DAMCL_RSA=2048,3072 ../..
To list other available CMake options, use:
sudo make uninstall
After having built the libraries you can build a binary installer and a source distribution by running this command
Start a command prompt as an administrator
git clone https://github.com/milagro-crypto/milagro-crypto-c cd milagro-crypto-c mkdir target\build cd target\build cmake -G "MinGW Makefiles" -D WORD_SIZE=64 ..\.. mingw32-make mingw32-make test mingw32-make doc mingw32-make install
Post install append the PATH system variable to point to the install ./lib:
My Computer -> Properties -> Advanced > Environment Variables
The build can be configured using by setting flags on the command line i.e.
cmake -G "MinGW Makefiles" -D WORD_SIZE=64 -D BUILD_PYTHON=on ..
After having built the libraries you can build a Windows installer using this command
sudo mingw32-make package
In order for this to work NSIS has to have been installed
This project includes a Makefile that allows you to test and build the project in a Linux-compatible system with simple commands. All the artifacts and reports produced using this Makefile are stored in the target folder.
All the packages listed in the Dockerfile are required in order to build and test all the library options in the current environment. Alternatively, everything can be built inside a Docker container using the command “make -f Makefile.docker buildall”.
To see all available options:
To build the builder Docker image:
make -f Makefile.docker
To build the project inside a Docker container (requires Docker) you need to build a builder image (once), and then build the project in its context:
make -f Makefile.docker buildall
To build a particular set of predefined makefile options inside a Docker container:
make -f Makefile.docker build TYPE=LINUX_64BIT_NIST256_RSA2048
or in the current environment:
make build TYPE=LINUX_64BIT_NIST256_RSA2048
To execute all the test builds and generate reports in the current environment:
To format the code (please use this command before submitting any pull request):
The following people have contributed to milagro-crypto-c
Please add yourself here if you make or have made a contribution.
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.
The Apache Software Foundation has classified this software as Export Commodity Control Number (ECCN) 5D002, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the “publicly available” Section 742.15(b) exemption (see the BIS Export Administration Regulations, Section 742.15(b)) for both object code and source code.
Apache Milagro 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.