|
(Page 1 of 8) 1 2 3 4 5 6 Next > Category: Cryptography » Libraries PHP_Sec (Wasp Project) Added 2004-10-07 PHP_Sec is a library for PHP, designed to detect possible Web attacks, use encryption and log information quickly and easily. The library acts as an IDS but at script level detecting possible SQL Injection, Cross Site Scripting, Directory Traversal, Evasion Techniques and various other vulnerabilties. By adding 2 lines of code we can protect any application PHP application in an easy way. yaSSL Added 2004-05-10 The yaSSL software package is a fast, dual-licensed implementation of SSL. It includes SSL client libraries and an SSL server implementation. It supports multiple APIs, including those defined by SSL and TLS. It also supports an OpenSSL compatibility interface. Qryptix Added 2004-04-28 Qryptix consists of a PAM object and utilities for session- and key-management for encrypted home directories using the International Kernel (CryptoAPI) patches for Linux. It simplifies login/logout, mounting/unmounting, and key generation and changing. XML Security Library Added 2004-04-15 XML Security Library is a C library based on LibXML2 and OpenSSL. The library was created with a goal to support major XML security standards: XML Signature and XML Encryption. GNU Transport Layer Security Library Added 2004-04-14 GNU Transport Layer Security Library is a library which implements a secure layer over a reliable transport layer such as TCP/IP. It implements the TLS 1.0 and SSL 3.0 protocols. GnuTLS is available for beta testing. Botan Added 2004-03-08 Botan is a library of cryptographic algorithms written in C++. It includes a wide selection of block and stream ciphers, public key algorithms, hash functions, and message authentication codes. It has an easy-to-use filter interface and supports many common industry standards, including X.509v3. The SSH library Added 2004-03-05 The SSH library is a C library to authenticate in a simple manner to one or more SSH servers. The goal of this project is to provide a library much simpler to use than OpenSSH's one. A sample SSH client is provided. Nettle library Added 2004-02-09 Nettle is a cryptographic library that is designed to fit easily in more or less any context: in crypto toolkits for object-oriented languages (C++, Python, Pike, etc.), in applications like LSH or GNUPG, or even in kernel space. In most contexts, you need more than the basic cryptographic algorithms; you also need some way to keep track of available algorithms and their properties and variants. You often have some algorithm selection process, often dictated by a protocol you want to implement. And as the requirements of applications differ in subtle and not so subtle ways, an API that fits one application well can be a pain to use in a different context, which is why there are so many different cryptographic libraries around. Nettle tries to avoid this problem by doing one thing, the low-level crypto stuff, and providing a @emph{simple} but general interface to it. In particular, Nettle doesn't do algorithm selection. It doesn't do memory allocation. It doesn't do any I/O. The idea is that one can build several application- and context-specific interfaces on top of Nettle and share the code, testcases, benchmarks, documentation, etc. For this first version, the only application using Nettle is LSH, and it uses an object-oriented abstraction on top of the library. GNU Generic Security Service Library Added 2004-01-22 Generic Security Service (GSS) is an implementation of the Generic Security Service API (GSSAPI). It is used by network applications to provide security services, such as authenticating SMTP/IMAP, via the GSSAPI SASL mechanism. It consists of a library and a manual, and a Kerberos 5 mechanism that supports mutual authentication and the DES and 3DES ciphers. GNU Simple Authentication and Security Layer (SASL) Added 2004-01-15 GNU SASL is a library that implements the IETF Simple Authentication and Security Layer (SASL) framework and some SASL mechanisms. SASL is used in servers (e.g. IMAP, SMTP, etc.) to request authentication from clients, and in clients to authenticate against servers. Browse by category |
|
|
Privacy Statement |
