Provides an interface to the SHA256 digest algorithm....

Provides an interface to the SHA3_256 digest algorithm....

Provides an interface to the SHA512_256 digest algorithm....

*Crypt::OpenPGP::Digest* is a factory class for PGP message digest objects. All digest objects are subclasses of this class and share a common interface; when creating a new digest object, the object is blessed into the subclass to take on algorithm-...

The "Digest::" modules calculate digests, also called "fingerprints" or "hashes", of some data, called a message. The digest is (usually) some small/fixed size string. The actual size of the digest depend of the algorithm used. The message is simply ...

This module provides common digests types for Moose, Moo, etc....

This module provides functions to calculate and verify Subresource Integrity hashes (SRI). All of the usage is shown in the "Synopsis", with some usage notes here: * The "sri" and "verify_sri" functions both accept either: * a filename as a plain sca...

Digest::SHA is written in C for speed. If your platform lacks a C compiler, you can install the functionally equivalent (but much slower) Digest::SHA::PurePerl module. The programming interface is easy to use: it's the same one found in CPAN's Digest...

SHA-2 is the collective name of one-way hash functions developed by the NIST. SHA-256, SHA-384, and SHA-512 pertain to hashes whose outputs are 256 bits, 384 bits and 512 bits, respectively. This Perl implementation is meant to be a replacement for t...

Provides an interface to various hash/digest algorithms....

Certain catalogues and protocols out there allow (or require) one to list several digests for a single file (or, rather, an octet sequence), provided that these are of different “kinds.” Consider, e. g., the "magnet:" URI schema, or Debian's “Package...

Digest::SHA::PurePerl is written entirely in Perl. If your platform has a C compiler, you should install the functionally equivalent (but much faster) Digest::SHA module. The programming interface is easy to use: it's the same one found in CPAN's Dig...

Packaging a benchmark script as a Bencher scenario makes it convenient to include/exclude/add participants/datasets (either via CLI or Perl code), send the result to a central repository, among others . See Bencher and bencher (CLI) for more details....