Algorithms

RIPEMD-320

RIPEMD-160 with both lines kept apart for 40 bytes. No stronger than RIPEMD-160 by design and it has HMAC
IDripemd32018 / 38RIPEMD · 320-bit
Hash / Cryptographic

RIPEMD-320

RIPEMD-160 at 40 bytes, and not a bit stronger.

Digest
320-bit · 40 bytes
HMAC
takes a key
Security
No stronger than RIPEMD-160: the wider digest adds no collision resistance
Family
5 in RIPEMD
4 options, 0 required

Sample

hex
0e12fe7d075f8e319e07c106917eddb0135e9a10aefb50a8a07ccb0582ff1fa27b95ed5af57fd5c6
base64
DhL+fQdfjjGeB8EGkX7dsBNemhCu+1CooHzLBYL/H6J7le1a9X/Vxg==

Options

encodingstring
default hex
Output encoding: hex, base64, base64url, binary
keystring
optional
HMAC key; enables HMAC mode
roundsnumber
default 1
How many times to hash, each round hashing the previous digest
chainstring
default bytes
What each round after the first hashes: bytes of the digest, or its lowercase hex

Access

Createcreate("ripemd320")
CLIhashes ripemd320 'hello world'
Tryplayground with the sample above
Kinripemd160, hash160, ripemd128, ripemd256

RIPEMD-160 runs two lines of five rounds and mixes them at the end. RIPEMD-320 keeps them apart. Each line gets its own start values, they swap one word after every round, and the digest is both lines side by side.

ts
create("ripemd320").hash("abc").digest;
// "de4c01b3054f8930a79d09ae738e92301e5a17085beffdc1b8d116713e74f82fa942d64cdbc4682d"

Twice the bytes, twice the security? No. The authors built it for apps that want a longer result, not more security. It's as strong as RIPEMD-160 and no more.

Nobody big uses it, and it's here anyway. A challenge that names it should find it somewhere.