cryptlib3.1

The library attempts to hide the low-level details of encryption/decryption and authentication from programmers, allowing them to quickly make their projects more secure.
Some of the symmetric encryption (private key) and authentication algorithms that cryptlib supports include the following:
· AES (Rijndael)
· Blowfish
· DES, 3DES
· RC2, RC4, RC5
The following hash algorithms are available in the library:
· MD2, MD4, MD5
· RIPEMD-160
· SHA
It offers services such as:
· S/MIME
· SSL/TLS
· ssh
It features various hashed message authentication code algorithms:
· HMAC-MD5, HMAC-SHA, HMAC-RIPEMD-160
Finally, asymmetric (public/private key) encryption algorithms such as the following are available:
· Diffie-Hellman, DSA, RSA
cryptlib can also be used with a variety of crypto devices (for example, Fortezza cards and Smart cards).
cryptlib contains as core components implementations of the most popular encryption and authentication algorithms, AES, Blowfish, CAST, DES, triple DES, IDEA, RC2, RC4, RC5, and Skipjack conventional encryption, MD2, MD4, MD5, RIPEMD-160 and SHA hash algorithms, HMAC-MD5, HMAC-SHA, and HMAC-RIPEMD-160 MAC algorithms, and Diffie-Hellman, DSA, Elgamal, and RSA public-key encryption.
In addition to these built-in capabilities, cryptlib can make use of the crypto capabilities of a variety of external crypto devices such as hardware security modules (HSMs), Fortezza cards, PKCS #11 devices, and crypto smart cards. The crypto device interface also provides a convenient general-purpose plug-in capability for adding new functionality which will be automatically used by cryptlib.
The library is free if used in personal, freeware, or shareware projects. The library is written in C. ActiveX and C++ wrappers are provided. The project is OSI Certified Open Source Software.
What's New in This Release:
· The final release contains mostly minor tweaks based on user feedback from the 3.1 final betas, with no noticeable external changes. Internally, the HTTP engine has been significantly improved, TLS 1.1 is now supported (although at release time there were no other known implementations of this to test against), the BeOS port has been re-done to handle the current state of the OS
using GNU development tools instead of the original Be ones (thanks to Simon Taylor for providing access to his system to do the work on), and the perpetual tweaking of the networking subsystem to handle OS-specific quirks has continued.