Tomb is a system to make strong encryption easy for everyday use. A tomb is like a locked folder that can be safely transported and hidden in a filesystem. Its keys can be kept separate; for example, you can keep the tomb on your computer and its key on a USB stick. Tomb is written in code that is easy to review and links shared components: it consists of a ZShell script and desktop integration apps; it uses standard GNU tools and the cryptographic API of the Linux kernel (dm-crypt) via cryptsetup.
PolarSSL is a light-weight cryptographic and SSL/TLS library written in C. PolarSSL makes it easy for developers to include cryptographic and SSL/TLS capabilities in their (embedded) applications with as little hassle as possible. Loose coupling of the components inside the library means that it is easy to separate the parts that are needed, without needing to include the total library. PolarSSL is written with embedded systems in mind and has been ported on a number of architectures, including ARM, PowerPC, MIPS, and Motorola 68000. The source is written to have very loose coupling, enabling easy integration of parts in other software projects. Very loosely coupled cryptographic algorithms for MD2, MD4, MD5, SHA1, SHA-256, SHA-512, AES, Camellia, DES, Triple DES, ARC3, and RSA are included.
jEncrypt is a commandline file encryption archiver. Files are encrypted with the AES-CTR mode, which was recommended by the National Institute of Standards and Technology in 2001 (NIST SP 800-38A). AES-CTR mode only provides confidentiality. It requires a message authentication code such as CBC-MAC to ensure an encrypted message is not accidentally modified or maliciously tampered with, which jEncrypt currently does not provide.
rfc3394 is a C# implementation of the RFC 3394 key-wrapping algorithm. The associated assembly provides two simple operations: one to wrap key data, and another to unwrap the key data. This code also includes a fairly comprehensive unit test library which, among other things, ensures that the implementation is verified against the test vectors provided in RFC 3394.
jQuery.pidCrypt uses HTML5 localStorage or sessionStorage for implementing an RSA public keyring within the browser, allowing transparent asymmetric encryption of form submissions while protecting the keys with AES symmetric encryption. It is easy to implement and has numerous configurable options for pre, post, and error-handling callbacks.