|Full description=Nettle is a cryptographic library designed to fit any context: in crypto toolkits for object-oriented languages, in applications like LSH or GNUPG, or even in kernel space. Users need to keep track of available algorithms and their properties and variants. The algorithm selection process is dictated by the protocol you want to implement. Also, requirements of applications differ, so an API that fits one application well may be useless for another (which is why so many different cryptographic libraries exist). Nettle avoids this problem by doing one thing, the low-level crypto stuff, and providing a simple but general interface to it. In particular, it doesn't do algorithm selection, memory allocation, or any I/O. However, users can build application- and context-specific interfaces on top of Nettle and share code, testcases, benchmarks, documentation, etc.

+

|Full description=Nettle is a cryptographic library designed to fit any context: in crypto toolkits for object-oriented languages, in applications like LSH or [[GnuPG]], or even in kernel space. Users need to keep track of available algorithms and their properties and variants. The algorithm selection process is dictated by the protocol you want to implement. Also, requirements of applications differ, so an API that fits one application well may be useless for another (which is why so many different cryptographic libraries exist). Nettle avoids this problem by doing one thing, the low-level crypto stuff, and providing a simple but general interface to it. In particular, it doesn't do algorithm selection, memory allocation, or any I/O. However, users can build application- and context-specific interfaces on top of Nettle and share code, testcases, benchmarks, documentation, etc.

Revision as of 13:29, 9 June 2014

GNU Nettle

http://www.lysator.liu.se/~nisse/nettle/Nettle is a cryptographic library designed to fit any context: in crypto toolkits for object-oriented languages, in applications like LSH or GnuPG, or even in kernel space. Users need to keep track of available algorithms and their properties and variants. The algorithm selection process is dictated by the protocol you want to implement. Also, requirements of applications differ, so an API that fits one application well may be useless for another (which is why so many different cryptographic libraries exist). Nettle avoids this problem by doing one thing, the low-level crypto stuff, and providing a simple but general interface to it. In particular, it doesn't do algorithm selection, memory allocation, or any I/O. However, users can build application- and context-specific interfaces on top of Nettle and share code, testcases, benchmarks, documentation, etc.

The copyright and license notices on this page only apply to the
text on this page. Any software or copyright-licenses or other
similar notices described in this text has its own copyright notice
and license, which can usually be found in the distribution or license
text itself.