- MESSAGE DIGESTS (HASH FUNCTIONS)
- SYMMETRIC ENCRYPTION
- RANDOM NUMBER GENERATION
- ASYMMETRIC CRYPTOGRAPHY
- BUGS AND FEEDBACK
- AUTHORS AND CONTRIBUTORS
- COPYRIGHT AND LICENSE
Crypt::Nettle - Perl interface to the Nettle Cryptographic library
Crypt::Nettle provides an object interface to the C nettle library. It currently supports message digests (including HMAC), symmetric encryption and decryption, pseudo-random number generation, and RSA public-key crypto.
In the future, it should also support DSA for public-key signatures.
See Crypt::Nettle::Hash for digest functions and HMAC.
See Crypt::Nettle::Cipher for symmetric encryption and decryption.
See Crypt::Nettle::Yarrow for a cryptographic random number generator.
The only public-key crypto algorithm supported by Crypt::Nettle at the moment is RSA. See Crypt::Nettle::RSA for details.
Crypt::Nettle has no known bugs, mostly because no one has reported any. Please mail to the author (email@example.com) with your contributions, comments, suggestions, bug reports or complaints.
Daniel Kahn Gillmor <firstname.lastname@example.org>
Copyright © Daniel Kahn Gillmor
Crypt::Nettle is free software, you may redistribute it and/or modify it under the GPL version 2 or later (your choice). Please see the COPYING file for the full text of the GPL.
This module was initially inspired by the GCrypt.pm bindings made by Alessandro Ranellucci.
This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 72:
Non-ASCII character seen before =encoding in '©'. Assuming UTF-8