Crypt::...PEMD128(3)

💖 Crypt::Digest::RIPEMD128 — the manual page, bestie edition 💖

okay so real quick before we dive in: this is a page from the User Contributed Perl Documentation (the Perl manual, iykyk), and it's literally all about Crypt::Digest::RIPEMD128. Buckle up 🎀

---

✨ NAME ✨

Crypt::Digest::RIPEMD128 — the RIPEMD-128 hash function, [size: 128 bits] 💅

---

🌸 SYNOPSIS 🌸

here's the whole vibe, copy-paste ready, no cap:

### Functional interface:
use Crypt::Digest::RIPEMD128 qw( ripemd128 ripemd128_hex ripemd128_b64 ripemd128_b64u
                             ripemd128_file ripemd128_file_hex ripemd128_file_b64 ripemd128_file_b64u );

# calculate digest from string/buffer
my $data = 'data string';
my $ripemd128_raw  = ripemd128($data);
my $ripemd128_hex  = ripemd128_hex($data);
my $ripemd128_b64  = ripemd128_b64($data);
my $ripemd128_b64u = ripemd128_b64u($data);
# or from file
my $ripemd128_file_raw  = ripemd128_file('filename.dat');
my $ripemd128_file_hex  = ripemd128_file_hex('filename.dat');
my $ripemd128_file_b64  = ripemd128_file_b64('filename.dat');
my $ripemd128_file_b64u = ripemd128_file_b64u('filename.dat');
# or from filehandle
my $filehandle = ...; # existing binary-mode filehandle
my $ripemd128_fh_raw  = ripemd128_file($filehandle);
my $ripemd128_fh_hex  = ripemd128_file_hex($filehandle);
my $ripemd128_fh_b64  = ripemd128_file_b64($filehandle);
my $ripemd128_fh_b64u = ripemd128_file_b64u($filehandle);

### OO interface:
use Crypt::Digest::RIPEMD128;

my $d = Crypt::Digest::RIPEMD128->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::RIPEMD128->new->addfile('filename.dat')->digest;

like, two whole interfaces — functional and OO — pick your fighter 🫶

---

🦋 DESCRIPTION 🦋

It gives you an interface to the RIPEMD128 digest algorithm. that's it, that's the whole description, and honestly? iconic. ✨

---

🎀 EXPORT 🎀

Nothing is exported by default. nothing. you gotta ask nicely 💅

You can export selected functions like this:

use Crypt::Digest::RIPEMD128 qw(ripemd128 ripemd128_hex ripemd128_b64 ripemd128_b64u
                                    ripemd128_file ripemd128_file_hex ripemd128_file_b64 ripemd128_file_b64u);

Or go full main-character and grab all of them at once:

use Crypt::Digest::RIPEMD128 ':all';

---

🔥 FUNCTIONS 🔥

⭐ ripemd128

Joins all its arguments into a single string, then hands you back its RIPEMD128 digest encoded as a binary string. raw bytes, no filter, we love that 💜

okay important detail about the data args, listen up: data arguments for the functional helpers get converted to byte strings using Perl's usual scalar stringification. defined scalars — numbers and string-overloaded objects included — are accepted, slay. undef is treated as an empty string and may emit Perl's usual uninitialized value warning. The same rules apply to ripemd128_hex, ripemd128_b64, and ripemd128_b64u. fr fr, same rules for all of them.

my $ripemd128_raw = ripemd128('data string');
#or
my $ripemd128_raw = ripemd128('any data', 'more data', 'even more data');

⭐ ripemd128_hex

Joins all the arguments into one single string and returns its RIPEMD128 digest encoded as a hexadecimal string. lowercase hex girlies rise 🌸

my $ripemd128_hex = ripemd128_hex('data string');
#or
my $ripemd128_hex = ripemd128_hex('any data', 'more data', 'even more data');

⭐ ripemd128_b64

Joins all the arguments into one string and returns its RIPEMD128 digest encoded as a Base64 string, with the trailing '=' padding. yes the padding stays, she's part of the look 💅

my $ripemd128_b64 = ripemd128_b64('data string');
#or
my $ripemd128_b64 = ripemd128_b64('any data', 'more data', 'even more data');

⭐ ripemd128_b64u

Joins all the arguments into one string and returns its RIPEMD128 digest encoded as a Base64 URL-safe string (see RFC 4648 section 5). url-safe, so she travels well 🦋

my $ripemd128_b64url = ripemd128_b64u('data string');
#or
my $ripemd128_b64url = ripemd128_b64u('any data', 'more data', 'even more data');

⭐ ripemd128_file

Reads a file — given by a filename or a filehandle — and returns its RIPEMD128 digest encoded as a binary string.

my $ripemd128_raw = ripemd128_file('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $ripemd128_raw = ripemd128_file($filehandle);

⭐ ripemd128_file_hex

Reads a file — filename or filehandle — and returns its RIPEMD128 digest encoded as a hexadecimal string.

my $ripemd128_hex = ripemd128_file_hex('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $ripemd128_hex = ripemd128_file_hex($filehandle);

⚠️ Note: the filehandle must be in binary mode before you pass it to addfile(). do not skip this step bestie, I'm begging 😭

⭐ ripemd128_file_b64

Reads a file — filename or filehandle — and returns its RIPEMD128 digest encoded as a Base64 string, with trailing '=' padding.

my $ripemd128_b64 = ripemd128_file_b64('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $ripemd128_b64 = ripemd128_file_b64($filehandle);

⭐ ripemd128_file_b64u

Reads a file — filename or filehandle — and returns its RIPEMD128 digest encoded as a Base64 URL-safe string (see RFC 4648 section 5).

my $ripemd128_b64url = ripemd128_file_b64u('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
my $ripemd128_b64url = ripemd128_file_b64u($filehandle);

---

👑 METHODS 👑

The OO interface provides 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::RIPEMD128->new();

🌈 new

my $d = Crypt::Digest::RIPEMD128->new();

fresh object, fresh start, main character energy ✨

🌈 clone

$d->clone();

🌈 reset

$d->reset();

🌈 add

Appends data to the message. Returns the object itself (for chaining — yes she chains, we love a fluent 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 energy as the functional side, fr.

$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).

$d->addfile('filename.dat');
#or
my $filehandle = ...; # existing binary-mode filehandle
$d->addfile($filehandle);

🌈 hashsize

$d->hashsize;
#or
Crypt::Digest::RIPEMD128->hashsize();
#or
Crypt::Digest::RIPEMD128::hashsize();

🌈 digest

Returns the binary digest (raw bytes). The first call finalizes the digest object — and heads up, bestie: any later add(), addfile(), digest(), hexdigest(), b64digest(), or b64udigest() call will fail until you call reset(). she's done after the first one, no take-backs 💀

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/RIPEMD>

---

and that's the whole page! 🍓 this lil doc shipped as perl v5.42.0, dated 2026-05-11, filed under Crypt::...PEMD128(3) — go forth and hash responsibly, ily, bye 💖✨🎀