Comparison of cryptography libraries
The tables below compare cryptography libraries that deal with cryptography algorithms and have api function calls to each of the supported features.
Cryptography libraries and their origin
Implementation | Company | Development Language | Open Source | Software License | FIPS 140 validated[1] | FIPS 140-2 mode | Latest Update | Origin |
Botan | Jack Lloyd | C++ | Yes | Simplified BSD | No | No | March 20, 2016 | USA |
Bouncy Castle | Legion of the Bouncy Castle | Java | Yes | MIT License | No | No | July 27, 2014 | Australia |
cryptlib | cryptlib | C | Yes | Sleepycat License and commercial license | No[lower-alpha 1] | Yes | March 25, 2016 | NZ |
Crypto++ | Crypto++ | C++ | Yes | Boost Software License 1.0, while the individual files in the compilation are all public domain | Yes | Yes | November 20, 2015 | |
Libgcrypt | GnuPG community and g10code | C | Yes | GNU LGPL v2.1+ | Yes | Yes | April 15, 2016 | Germany |
libsodium | Frank Denis | C | Yes | ISC license | No | No | April 4, 2016 | France |
NaCl | | C, C++ | Yes | Public Domain | No | No | 2013 | |
Nettle | | C | Yes | GNU GPL v2, GNU LGPL v3 | No | No | January 7, 2013 | Sweden |
OpenSSL | The OpenSSL Project | C | Yes | Apache Licence 1.0 or 4-Clause BSD Licence | No | No | March 1, 2016 | |
wolfCrypt | wolfSSL, Inc. | C | Yes | GPL v2 and commercial license | Yes | Yes | December 5, 2014 | USA |
- ↑ The actual cryptlib is not FIPS 140 validated, although a validation exists for an adapted cryptlib as part of a third party, proprietary, commercial product.
Key operations
Key operations include key generation algorithms, key exchange agreements and public key cryptography standards.
Key generation and exchange
- ↑ By using the lower level interface.
Public key cryptography standards
- 1 2 3 4 5 These Public Key Cryptographic Standards (PKCS) are supported by accompanying libraries and tools, which are also part of the GnuPG framework, although not by the actual libgcrypt library.
Hash functions
Comparison of supported cryptographic hash functions. At the moment this section also includes ciphers that are used for producing a MAC tag for a message. Here hash functions are defined as taking an arbitrary length message and producing a fixed size output that is virtually impossible to use for recreating the original message.
MAC algorithms
Comparison of implementations of message authentication code (MAC) algorithms. A MAC is a short piece of information used to authenticate a message—in other words, to confirm that the message came from the stated sender (its authenticity) and has not been changed in transit (its integrity).
Block ciphers
Table compares implementations of block ciphers. Block ciphers are defined as being deterministic and operating on a set number of bits (termed a block) using a symmetric key. Each block cipher where applicable is broken up into the possible key size and what mode it can be run with, i.e. CBC, CTR.
Stream ciphers
Table compares implementations of the various stream ciphers. Stream ciphers are defined as using plain text digits that are combined with a pseudorandom cipher digit stream. Stream ciphers are typically faster than block ciphers and may have lower hardware complexity, but may be more susceptible to attacks.
Hardware-assisted support
Table compares the ability to utilize hardware enhanced cryptography. With using the assistance of specific hardware the library can achieve faster speeds than otherwise. This is done through hardware that has been designed in such a way as to handle cryptography better.
Code size
Portability
Implementation |
Supported Operating System |
Thread safe |
libsodium |
OS X, Linux, OpenBSD, NetBSD, FreeBSD, DragonflyBSD, Android, iOS, 32 and 64-bit Windows (Visual Studio, MinGW, C++ Builder), NativeClient, QNX, Javascript, AIX, Minix, Solaris |
Yes |
cryptlib |
AMX, BeOS, ChorusOS, DOS, eCOS, FreeRTOS/OpenRTOS, uItron, MVS, OS/2, Palm OS, QNX Neutrino, RTEMS, Tandem NonStop, ThreadX, uC/OS II, Unix (AIX, FreeBSD, HPUX, Linux, OS X, Solaris, etc.), VDK, VM/CMS, VxWorks, Win16, Win32, Win64, WinCE/PocketPC/etc, XMK |
Yes |
Crypto++ |
Unix (OpenBSD, Linux, OS X, etc.), Win32, Win64, Android, iOS, ARM |
|
Libgcrypt |
All 32 bit and 64 bit Unix Systems, Win32, WinCE |
Yes[9] |
wolfCrypt |
Win32/64, Linux, Mac OS X, Solaris, ThreadX, VxWorks, FreeBSD, NetBSD, OpenBSD, embedded Linux, WinCE, Haiku, OpenWRT, iPhone (iOS), Android, Nintendo Wii and Gamecube through DevKitPro, QNX, MontaVista, NonStop, TRON/ITRON/µITRON, Micrium's µC/OS, FreeRTOS, SafeRTOS, Freescale MQX, Nucleus, TinyOS, HP/UX |
Yes |
References
- ↑ Validated FIPS 140 Cryptographic Modules, NIST.gov, retrieved 2015-12-22
- ↑ Bouncy Castle Specifications, bouncycastle.org, retrieved 2015-11-28
- ↑ cryptlib Encryption Toolkit, Peter Gutmann, retrieved 2015-11-28
- ↑ Crypto++ Library, Cryptopp.com, retrieved 2015-11-28
- 1 2 Language Analysis of Bouncy Castle, OpenHub.net, retrieved 2015-12-23
- 1 2 Language Analysis of Crypto++, OpenHub.net, retrieved 2015-12-23
- 1 2 Language Analysis of Libgcrypt, OpenHub.net, retrieved 2015-12-23
- 1 2 Language Analysis of Nettle, OpenHub.net, retrieved 2015-12-23
- ↑ GnuPG documentation: Libgcrypt overview - thread safety, GnuPG.org, retrieved 2016-04-16
External links