Crypt::...SHA3_384(3)
π NAME π
Crypt::Digest::SHA3_384 β the hash function SHA3-384, bestie! [size: 384 bits] β¨
πΈ SYNOPSIS πΈ
okay so here's the whole vibe, functional style first:
### Functional interface:
use Crypt::Digest::SHA3_384 qw( sha3_384 sha3_384_hex sha3_384_b64 sha3_384_b64u
sha3_384_file sha3_384_file_hex sha3_384_file_b64 sha3_384_file_b64u );
# calculate digest from string/buffer
my $data = 'data string';
my $sha3_384_raw = sha3_384($data);
my $sha3_384_hex = sha3_384_hex($data);
my $sha3_384_b64 = sha3_384_b64($data);
my $sha3_384_b64u = sha3_384_b64u($data);
# or from file
my $sha3_384_file_raw = sha3_384_file('filename.dat');
my $sha3_384_file_hex = sha3_384_file_hex('filename.dat');
my $sha3_384_file_b64 = sha3_384_file_b64('filename.dat');
my $sha3_384_file_b64u = sha3_384_file_b64u('filename.dat');
# or from filehandle
my $filehandle = ...; # existing binary-mode filehandle
my $sha3_384_fh_raw = sha3_384_file($filehandle);
my $sha3_384_fh_hex = sha3_384_file_hex($filehandle);
my $sha3_384_fh_b64 = sha3_384_file_b64($filehandle);
my $sha3_384_fh_b64u = sha3_384_file_b64u($filehandle);
### OO interface:
use Crypt::Digest::SHA3_384;
my $d = Crypt::Digest::SHA3_384->new;
$d->add('any data');
my $result_raw = $d->digest; # raw bytes
my $result_hex = $d->hexdigest; # hexadecimal form
my $result_b64 = $d->b64digest; # Base64 form
my $result_b64u = $d->b64udigest; # Base64 URL-safe form
# or hash a file instead
my $file_result_raw = Crypt::Digest::SHA3_384->new->addfile('filename.dat')->digest;
π¦ DESCRIPTION π¦
It gives you an interface to the SHA3_384 digest algorithm. that's the whole thing, she's simple, she's iconic π
π EXPORT π
By default? nothing gets exported. absolutely nothing, no cap.
But you can export selected functions, if that's your vibe:
use Crypt::Digest::SHA3_384 qw(sha3_384 sha3_384_hex sha3_384_b64 sha3_384_b64u
sha3_384_file sha3_384_file_hex sha3_384_file_b64 sha3_384_file_b64u);
Or literally all of them at once, go off queen:
use Crypt::Digest::SHA3_384 ':all';
β¨ FUNCTIONS β¨
π sha3_384
Joins all your arguments into one single string and returns its SHA3_384 digest, encoded as a binary string.
Data arguments for the functional helpers get converted to byte strings using Perl's usual scalar stringification. Defined scalars β including numbers and string-overloaded objects β are accepted. undef is treated as an empty string and may emit Perl's usual "uninitialized value" warning. Same rules apply to sha3_384_hex, sha3_384_b64, and sha3_384_b64u. π«Ά
my $sha3_384_raw = sha3_384('data string');
#or
my $sha3_384_raw = sha3_384('any data', 'more data', 'even more data');
π sha3_384_hex
Joins all your arguments into one single string and returns its SHA3_384 digest, encoded as a hexadecimal string.
my $sha3_384_hex = sha3_384_hex('data string');
#or
my $sha3_384_hex = sha3_384_hex('any data', 'more data', 'even more data');
π sha3_384_b64
Joins all your arguments into one single string and returns its SHA3_384 digest, encoded as a Base64 string, with trailing '=' padding. β¨
my $sha3_384_b64 = sha3_384_b64('data string');
#or
my $sha3_384_b64 = sha3_384_b64('any data', 'more data', 'even more data');
π sha3_384_b64u
Joins all your arguments into one single string and returns its SHA3_384 digest, encoded as a Base64 URL-safe string (see RFC 4648 section 5). iykyk π
my $sha3_384_b64url = sha3_384_b64u('data string');
#or
my $sha3_384_b64url = sha3_384_b64u('any data', 'more data', 'even more data');
π sha3_384_file
Reads a file β given by a filename or a filehandle β and returns its SHA3_384 digest, encoded as a binary string.
my $sha3_384_raw = sha3_384_file('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $sha3_384_raw = sha3_384_file($filehandle);
π sha3_384_file_hex
Reads a file β given by a filename or a filehandle β and returns its SHA3_384 digest, encoded as a hexadecimal string.
my $sha3_384_hex = sha3_384_file_hex('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $sha3_384_hex = sha3_384_file_hex($filehandle);
β οΈ Note: the filehandle must be in binary mode before you pass it to addfile(). don't skip this step bestie, it's giving "why is my hash wrong" π
π sha3_384_file_b64
Reads a file β given by a filename or a filehandle β and returns its SHA3_384 digest, encoded as a Base64 string, with trailing '=' padding.
my $sha3_384_b64 = sha3_384_file_b64('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $sha3_384_b64 = sha3_384_file_b64($filehandle);
π sha3_384_file_b64u
Reads a file β given by a filename or a filehandle β and returns its SHA3_384 digest, encoded as a Base64 URL-safe string (see RFC 4648 section 5). π
my $sha3_384_b64url = sha3_384_file_b64u('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $sha3_384_b64url = sha3_384_file_b64u($filehandle);
π METHODS π
The OO interface gives you the same set of functions as Crypt::Digest. Unless noted otherwise, just assume $d is an existing digest object created via new, like this:
my $d = Crypt::Digest::SHA3_384->new();
π new
my $d = Crypt::Digest::SHA3_384->new();
π clone
$d->clone();
π reset
$d->reset();
π add
Appends data to the message. Returns the object itself (so you can chain, slay π ).
Each argument gets converted to bytes using Perl's usual scalar stringification. Defined scalars β including numbers and string-overloaded objects β are accepted. undef is treated as an empty string and may emit Perl's usual "uninitialized value" warning.
$d->add('any data');
#or
$d->add('any data', 'more data', 'even more data');
π addfile
Reads the file content and appends it to the message. Returns the object itself (chaining again, we love to see it).
$d->addfile('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
$d->addfile($filehandle);
π hashsize
$d->hashsize;
#or
Crypt::Digest::SHA3_384->hashsize();
#or
Crypt::Digest::SHA3_384::hashsize();
π digest
Returns the binary digest (raw bytes). The first call finalizes the digest object β so any later add(), addfile(), digest(), hexdigest(), b64digest(), or b64udigest() call will fail until you call reset(). π« that's the main-character rule, no exceptions.
my $result_raw = $d->digest();
π hexdigest
Returns the digest encoded as a lowercase hexadecimal string. Like digest(), the first call finalizes the digest object.
my $result_hex = $d->hexdigest();
π b64digest
Returns the digest encoded as a Base64 string with trailing "=" padding. Like digest(), the first call finalizes the digest object.
my $result_b64 = $d->b64digest();
π b64udigest
Returns the digest encoded as a Base64 URL-safe string (no trailing "="). Like digest(), the first call finalizes the digest object.
my $result_b64url = $d->b64udigest();
π SEE ALSO π
CryptX,Crypt::Digest- <https://en.wikipedia.org/wiki/SHA-3>
okay that's the whole page, you ate that π«Ά this was perl v5.42.0, dated 2026-05-11, filed under Crypt::...SHA3_384(3) β go hash something iconic, bestie πππ¦
π¦ where this page comes from
- opensuse-leap 16.0: perl-CryptX 0.89.0-bp160.1.1 Β· Artistic-1.0 OR GPL-1.0-or-later
- opensuse-leap 16.0: perl-CryptX 0.89.0-bp160.1.1 Β· Artistic-1.0 OR GPL-1.0-or-later
- opensuse-leap 16.0: perl-CryptX 0.89.0-bp160.1.1 Β· Artistic-1.0 OR GPL-1.0-or-later
- opensuse-leap 16.0: perl-CryptX 0.89.0-bp160.1.1 Β· Artistic-1.0 OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms