Crypt::...E2s_128(3)
π Crypt::Digest::BLAKE2s_128 β the manual, but make it make sense π
okay so bestie, welcome to the Crypt::...E2s_128(3) page β¨ this is the perl doc for Crypt::Digest::BLAKE2s_128 and honestly? it's giving "small but mighty" π¦ a whole hash function living its best life at 128 bits and i'm obsessed.
πΈ NAME πΈ
Crypt::Digest::BLAKE2s_128 β Hash function BLAKE2s [size: 128 bits] π
like, it hashes stuff. that's the whole vibe. no cap.
β¨ SYNOPSIS β¨
two ways to do the thing, and both ate π first up, the functional interface:
### Functional interface:
use Crypt::Digest::BLAKE2s_128 qw( blake2s_128 blake2s_128_hex blake2s_128_b64 blake2s_128_b64u
blake2s_128_file blake2s_128_file_hex blake2s_128_file_b64 blake2s_128_file_b64u );
# calculate digest from string/buffer
my $data = 'data string';
my $blake2s_128_raw = blake2s_128($data);
my $blake2s_128_hex = blake2s_128_hex($data);
my $blake2s_128_b64 = blake2s_128_b64($data);
my $blake2s_128_b64u = blake2s_128_b64u($data);
# or from file
my $blake2s_128_file_raw = blake2s_128_file('filename.dat');
my $blake2s_128_file_hex = blake2s_128_file_hex('filename.dat');
my $blake2s_128_file_b64 = blake2s_128_file_b64('filename.dat');
my $blake2s_128_file_b64u = blake2s_128_file_b64u('filename.dat');
# or from filehandle
my $filehandle = ...; # existing binary-mode filehandle
my $blake2s_128_fh_raw = blake2s_128_file($filehandle);
my $blake2s_128_fh_hex = blake2s_128_file_hex($filehandle);
my $blake2s_128_fh_b64 = blake2s_128_file_b64($filehandle);
my $blake2s_128_fh_b64u = blake2s_128_file_b64u($filehandle);
### OO interface:
use Crypt::Digest::BLAKE2s_128;
my $d = Crypt::Digest::BLAKE2s_128->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::BLAKE2s_128->new->addfile('filename.dat')->digest;
the chaining at the end?? main character energy, honestly π₯
π¦ DESCRIPTION π¦
It provides an interface to the BLAKE2s_128 digest algorithm. that's it, that's the whole description, and she said what she said πββοΈ
π EXPORT π
Nothing is exported by default. shy queen behavior π
You can export selected functions:
use Crypt::Digest::BLAKE2s_128 qw(blake2s_128 blake2s_128_hex blake2s_128_b64 blake2s_128_b64u
blake2s_128_file blake2s_128_file_hex blake2s_128_file_b64 blake2s_128_file_b64u);
Or all of them at once β go big or go home, periodt:
use Crypt::Digest::BLAKE2s_128 ':all';
π FUNCTIONS π
β blake2s_128
Joins all arguments into a single string and returns its BLAKE2s_128 digest encoded as a binary string. raw bytes, no filter, we love that for her π
Data arguments for the functional helpers are 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 π and yes, the same rules apply to blake2s_128_hex, blake2s_128_b64, and blake2s_128_b64u. so don't come for me when the warning shows up.
my $blake2s_128_raw = blake2s_128('data string');
#or
my $blake2s_128_raw = blake2s_128('any data', 'more data', 'even more data');
π blake2s_128_hex
Joins all arguments into a single string and returns its BLAKE2s_128 digest encoded as a hexadecimal string. lowercase hex girly β¨
my $blake2s_128_hex = blake2s_128_hex('data string');
#or
my $blake2s_128_hex = blake2s_128_hex('any data', 'more data', 'even more data');
π blake2s_128_b64
Joins all arguments into a single string and returns its BLAKE2s_128 digest encoded as a Base64 string, with trailing '=' padding. the padding stays, she's not going anywhere π
my $blake2s_128_b64 = blake2s_128_b64('data string');
#or
my $blake2s_128_b64 = blake2s_128_b64('any data', 'more data', 'even more data');
π§ blake2s_128_b64u
Joins all arguments into a single string and returns its BLAKE2s_128 digest encoded as a Base64 URL-safe string (see RFC 4648 section 5). url-safe so it can go anywhere without causing drama πΈ
my $blake2s_128_b64url = blake2s_128_b64u('data string');
#or
my $blake2s_128_b64url = blake2s_128_b64u('any data', 'more data', 'even more data');
π blake2s_128_file
Reads a file given by a filename or filehandle and returns its BLAKE2s_128 digest encoded as a binary string.
my $blake2s_128_raw = blake2s_128_file('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $blake2s_128_raw = blake2s_128_file($filehandle);
π blake2s_128_file_hex
Reads a file given by a filename or filehandle and returns its BLAKE2s_128 digest encoded as a hexadecimal string.
my $blake2s_128_hex = blake2s_128_file_hex('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $blake2s_128_hex = blake2s_128_file_hex($filehandle);
β οΈ Note: The filehandle must be in binary mode before you pass it to addfile(). no cap, if it's not binary mode things get weird and not in a fun way π
πΈ blake2s_128_file_b64
Reads a file given by a filename or filehandle and returns its BLAKE2s_128 digest encoded as a Base64 string, with trailing '=' padding.
my $blake2s_128_b64 = blake2s_128_file_b64('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $blake2s_128_b64 = blake2s_128_file_b64($filehandle);
π¦ blake2s_128_file_b64u
Reads a file given by a filename or filehandle and returns its BLAKE2s_128 digest encoded as a Base64 URL-safe string (see RFC 4648 section 5).
my $blake2s_128_b64url = blake2s_128_file_b64u('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $blake2s_128_b64url = blake2s_128_file_b64u($filehandle);
π«Ά METHODS π«Ά
The OO interface provides the same set of functions as Crypt::Digest. Unless noted otherwise, assume $d is an existing digest object created via new, for example:
my $d = Crypt::Digest::BLAKE2s_128->new();
π« new
makes you a fresh digest object, brand new, never used π
my $d = Crypt::Digest::BLAKE2s_128->new();
π« clone
copies the object. twin moment π―ββοΈ
$d->clone();
π« reset
wipes it back to blank so you can start over. we love a fresh start β¨
$d->reset();
π« add
Appends data to the message. Returns the object itself (for chaining). chainable queen π
Each argument is 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. same rules, same energy π
$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 (for chaining). yes, also chainable π
$d->addfile('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
$d->addfile($filehandle);
π« hashsize
tells you the hash size. three ways to ask, all valid, pick your fighter π₯
$d->hashsize;
#or
Crypt::Digest::BLAKE2s_128->hashsize();
#or
Crypt::Digest::BLAKE2s_128::hashsize();
π« digest
Returns the binary digest (raw bytes). The first call finalizes the digest object. Any later add(), addfile(), digest(), hexdigest(), b64digest(), or b64udigest() call will fail until you call reset(). like, she's done, she's clocked out, do not bother her π€
my $result_raw = $d->digest();
π« hexdigest
Returns the digest encoded as a lowercase hexadecimal string. Like digest(), the first call finalizes the digest object. same rules, same doors-closed energy πͺ
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. no padding, she travels light π§³
my $result_b64url = $d->b64udigest();
π₯ SEE ALSO π₯
- CryptX, Crypt::Digest β the whole family, go say hi π
- <https://blake2.net/> β the official site, iconic
- <https://www.rfc-editor.org/rfc/rfc7693> β the RFC, for when you want the lore π
and that's the whole page bestie π go hash something and slay β¨
source/version + date tea: this is from perl v5.42.0, dated 2026-05-11, and the page you're reading is Crypt::...E2s_128(3) β mwah, bye π
π¦ 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