|News||Platforms||Download||Manual||GitHub||Mediawiki||Mailing lists||Contributions||Related links|
Crypto++ Library is a free C++ class library of cryptographic schemes. The library contains the following algorithms:
|authenticated encryption schemes||GCM, CCM, EAX, ChaCha20Poly1305, XChaCha20Poly1305|
|high speed stream ciphers||ChaCha (8/12/20), ChaCha (IETF) HC (128/256), Panama, Rabbit (128/256), Sosemanuk, Salsa20 (8/12/20), XChaCha (8/12/20), XSalsa20|
|AES and AES candidates||AES (Rijndael), RC6, MARS, Twofish, Serpent, CAST-256|
|other block ciphers||ARIA, Blowfish, Camellia, CHAM, HIGHT, IDEA, Kalyna (128/256/512), LEA, SEED, RC5, SHACAL-2, SIMECK, SIMON (64/128), Skipjack, SPECK (64/128), Simeck, SM4,Threefish (256/512/1024), Triple-DES (DES-EDE2 and DES-EDE3), TEA, XTEA|
|block cipher modes of operation||ECB, CBC, CBC ciphertext stealing (CTS), CFB, OFB, counter mode (CTR)|
|message authentication codes||BLAKE2b, BLAKE2s, CMAC, CBC-MAC, DMAC, GMAC (GCM), HMAC, Poly1305, SipHash, Two-Track-MAC, VMAC|
|hash functions||BLAKE2b, BLAKE2s, Keccack (F1600), SHA-1, SHA-2, SHA-3, SHAKE (128/256), SipHash, Tiger, RIPEMD (128/160/256/320), SM3, WHIRLPOOL|
|public-key cryptography||RSA, DSA, Determinsitic DSA (RFC 6979), ElGamal, Nyberg-Rueppel (NR), Rabin-Williams (RW), EC-based German Digital Signature (ECGDSA), LUC, LUCELG, DLIES (variants of DHAES), ESIGN|
|padding schemes for public-key systems||PKCS#1 v2.0, OAEP, PSS, PSSR, IEEE P1363 EMSA2 and EMSA5|
|key agreement schemes||Diffie-Hellman (DH), Unified Diffie-Hellman (DH2), Menezes-Qu-Vanstone (MQV), Hashed MQV (HMQV), Fully Hashed MQV (FHMQV), LUCDIF, XTR-DH|
|elliptic curve cryptography||ECDSA, Determinsitic ECDSA (RFC 6979), ed25519, ECGDSA, ECNR, ECIES, x25519, ECDH, ECMQV|
|insecure or obsolescent algorithms retained for backwards compatibility and historical value||MD2, MD4, MD5, Panama Hash, DES, ARC4, SEAL 3.0, WAKE-OFB, DESX (DES-XEX3), RC2, SAFER, 3-WAY, GOST, SHARK, CAST-128, Square|
Other features include:
Crypto++ Library is copyrighted as a compilation and (as of version 5.6.2) licensed under the Boost Software License 1.0, while the individual files in the compilation are all public domain.
The current version of Crypto++ supports the following compilers:
For detailed build status and notes on various compiler/OS/CPU combinations as well as information about compiling earlier versions of Crypto++, please see this wiki entry.
The following is a short list of recent releases and other news. For the complete list please see History.txt.
The downloads for the most recent Crypto++ libraries from the last several years are below. If you need older downloads, from Crypto++ 5.5 to Crypto++ 2.3, then visit the Downloads page. The Downloads page provides checksums for all releases hosted on the website. Release signatures can be verified using GnuPG according to Release Signing.
|2019-04-28||Crypto++ 8.2.0 [sig]||8.2.0 Release||Crypto++ 8.2.0|
|2019-02-22||Crypto++ 8.1.0 [sig]||8.1.0 Release||Crypto++ 8.1.0|
|2018-12-28||Crypto++ 8.0.0 [sig]||8.0.0 Release||Crypto++ 8.0.0|
|2018-04-08||Crypto++ 7.0.0 [sig]||7.0.0 Release||Crypto++ 7.0.0|
|2018-02-22||Crypto++ 6.1.0 [sig]||6.1.0 Release||Crypto++ 6.1.0|
|2018-01-22||Crypto++ 6.0.0 [sig]||6.0.0 Release||Crypto++ 6.0.0|
|2016-10-11||Crypto++ 5.6.5 [sig]||5.6.5 Release||Crypto++ 5.6.5|
|2016-09-11||Crypto++ 5.6.4 [sig]||5.6.4 Release||Crypto++ 5.6.4|
|2015-11-20||Crypto++ 5.6.3 [sig]||5.6.3 Release||Crypto++ 5.6.3|
|2013-02-20||Crypto++ 5.6.2 [sig]||5.6.2 Release||Crypto++ 5.6.2|
Remember to use the "-a" auto-convert text files option when unzipping on a Unix machine. After downloading, please read the Readme.txt included in the zip archive for build instructions and other important notes.
Crypto++ is listed on the CMVP's Historical Validation List. It effectively means the library is no longer validated. If you are interested in sponsoring a validation, then please send a message to the mailing list to start an offline conversation.
There are two mailing lists for Crypto++. The first is email@example.com, and the second is firstname.lastname@example.org.
As a courtesy, please join the discussion list with your real name instead of an online handle. Alternate webviews are for the lists are available at Crypto++ Announce - Google Groups and Crypto++ Users - Google Groups.
When posting a question to the Crypto++ user mailing list, please provide the following information, if applicable:
Crypto++ attempts to resist side channel attacks using various remediations. We believe the library is hardened but the remdiations may be incomplete. The first line of defense uses hardware instructions when possible. The library also uses cache-aware algoirthms and access patterns to minimize leakage. If you suspect or find an information leak then please report it.
Crypto++ does not enagage Specter remediations at this time. The GCC options for Specter are -mfunction-return=thunk and -mindirect-branch=thunk. If you want the Specter workarounds then add the GCC options to your CXXFLAGS when building the library. The library tests uses the options and they should work as expected.
The source code and its planned changes are available at the following locations.
Contributions of all types are welcomed. Contributions include the following.
If you think you have found a bug in the library, then you should discuss it on the Users mailing list. Discussing it will help bring the issue to the attention of folks who can help resolve the issue. If you want to contribute a bug fix to the library, then make a Pull Request or make a Diff available somewhere. Also see Bug Reports on the wiki.
Features and enhancements are welcomend additions to the library. This category tends to be time consuming because algorithms and their test cases need to be reviewed and merged. Please be mindful of the test cases, and attempt to procure them from an independent source.
The library cherishes test scripts and test cases. They ensure the library is fit and they help uncover issues with the library before users experience them. If you have some time, then write some test cases, especially the ones that are intended to break things.
Branch and release testing is your chance to ensure Master (and planned merges) meets your expectations and perform as expected. If you have a few spare cycles, then please test Master on your favorite platform. We need more testing on MinGW, Windows Phone, Windows Store, Solaris 10 (and below), and modern iOS and OS X (including TV and Watch builds).
Documentation and updates includes both the inline source code annotations using Doxygen, and the online information provided in the wiki. The wiki is more verbose and usually provides more contextual information than the API reference. Besides testing, documentation is one of the highest returns on investment.
If you are interested in paid support for Crypto++ or consulting on a Crypto++ related project, then please see this list of companies and individuals providing services on the wiki. This listing is a free service for the Crypto++ community, and anyone may sign up to be listed by creating an account on the wiki.
|Visitors since April 2014.|
|Originally written by Wei Dai||Last modified: April 28, 2019||Currently maintained by the Crypto++ community|