RIPEMD160_FileChunk3
Calculate the ripemd160 message digest
Part of RIPEMD160_Data(3).
Usage
void
void
void
char *
char *
char *
char *
char *
char *
Library
library “libmd”
Overview
The RIPEMD160_ functions calculate a 160-bit cryptographic checksum (digest) for any number of input bytes. A cryptographic checksum is a one-way hash function; that is, it is computationally impractical to find the input corresponding to a particular output. This net result is a “fingerprint” of the input-data, which does not disclose the actual input.
The RIPEMD160_Init(), RIPEMD160_Update(), and RIPEMD160_Final() functions are the core functions. Allocate an RIPEMD160_CTX, initialize it with RIPEMD160_Init(), run over the data with RIPEMD160_Update(), and finally extract the result using RIPEMD160_Final(), which will also erase the RIPEMD160_CTX.
The RIPEMD160_End() function is a wrapper for RIPEMD160_Final() which converts the return value to a 41-character (including the terminating '\0') ASCII string which represents the 160 bits in hexadecimal.
The RIPEMD160_File() function calculates the digest of a file, and uses RIPEMD160_End() to return the result. If the file cannot be opened, a null pointer is returned. The RIPEMD160_FileChunk() function is similar to RIPEMD160_File(), but it only calculates the digest over a byte-range of the file specified, starting at offset and spanning length bytes. If the length parameter is specified as 0, or more than the length of the remaining part of the file, RIPEMD160_FileChunk() calculates the digest from offset to the end of file. The RIPEMD160_Data() function calculates the digest of a chunk of data in memory, and uses RIPEMD160_End() to return the result.
The RIPEMD160_Fd() and RIPEMD160_FdChunk() functions are identical to their RIPEMD160_File() and RIPEMD160_FileChunk() counterparts, with the exception that the first argument is an fd instead of a filename.
When using RIPEMD160_End(), RIPEMD160_File(), or RIPEMD160_Data(), the buf argument can be a null pointer, in which case the returned string is allocated with malloc(3) and subsequently must be explicitly deallocated using free(3) after use. If the buf argument is non-null it must point to at least 41 characters of buffer space.
Errors
The RIPEMD160_End() function called with a null buf argument may fail and return NULL if:
- [ENOMEM]
-
Insufficient storage space is available.
The RIPEMD160_File() and RIPEMD160_FileChunk() may return NULL when underlying open(2), fstat(2), lseek(2), or RIPEMD160_End(3) fail.
History
- FreeBSD 16.0-CURRENT (2026-10-27) to FreeBSD 15.0-RELEASE: the text shown here
- FreeBSD 14.5-RELEASE to FreeBSD 14.0-RELEASE
- FreeBSD 13.5-RELEASE to FreeBSD 13.3-RELEASE
- FreeBSD 13.2-RELEASE
- FreeBSD 13.1-RELEASE to FreeBSD 13.0-RELEASE
- FreeBSD 12.4-RELEASE
- FreeBSD 12.3-RELEASE
- FreeBSD 12.2-RELEASE
- FreeBSD 12.1-RELEASE
- FreeBSD 12.0-RELEASE
- FreeBSD 11.4-RELEASE
- FreeBSD 11.3-RELEASE
- FreeBSD 11.2-RELEASE
- FreeBSD 11.1-RELEASE
- FreeBSD 11.0-RELEASE
- FreeBSD 10.4-RELEASE
- FreeBSD 10.3-RELEASE
- FreeBSD 10.2-RELEASE
- FreeBSD 10.1-RELEASE
- FreeBSD 10.0-RELEASE
- FreeBSD 9.3-RELEASE
- FreeBSD 9.2-RELEASE
- FreeBSD 9.1-RELEASE
- FreeBSD 9.0-RELEASE
- FreeBSD 8.4-RELEASE
- FreeBSD 8.3-RELEASE
- FreeBSD 8.2-RELEASE
- FreeBSD 8.1-RELEASE
- FreeBSD 8.0-RELEASE
- FreeBSD 7.4-RELEASE
- FreeBSD 7.3-RELEASE
- FreeBSD 7.2-RELEASE
- FreeBSD 7.1-RELEASE
- FreeBSD 7.0-RELEASE
- FreeBSD 6.4-RELEASE
- FreeBSD 6.3-RELEASE to FreeBSD 6.0-RELEASE
- FreeBSD 5.5-RELEASE to FreeBSD 5.3-RELEASE
- FreeBSD 5.2.1-RELEASE to FreeBSD 5.2-RELEASE
- FreeBSD 5.1-RELEASE
- FreeBSD 5.0-RELEASE