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.
DocumentationUser manual included and available in HTML format from http://www.lysator.liu.se/~nisse/nettle/nettle.html
This is a GNU package:nettle
released on 1 October 2016
|License||Verified by||Verified on||Notes|
|LGPLv3orlater||Genium||25 April 2015|
|GPLv2||Genium||25 April 2015|
|GPLv3||Genium||25 April 2015|
Leaders and contributors
Resources and communication
|Developer||VCS Repository Webview||https://git.lysator.liu.se/nettle/nettle|
|Developer||Bug Tracking Subscribe||https://lists.lysator.liu.se/mailman/listinfo/nettle-bugs|
This entry (in part or in whole) was last reviewed on 5 January 2017.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
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.