Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

trf_mdupdatebuf(3) [debian man page]

Trf_MDUpdateBuf(3)					     Library Functions Manual						Trf_MDUpdateBuf(3)

Trf_MDUpdateBuf - Interface to procedures for update of a MD context. SYNOPSIS
#include <transform.h> void Trf_MDUpdateBuf ( void *context, unsigned char *buf, int bufLen ); PARAMETERS
void *context State to update. unsigned char *buf Buffer to hash into the state. int bufLen Number of characters in the buffer. DESCRIPTION
A procedure of this type is called for character buffer to hash into the final digest. This procedure is optional, its definition has precedence over 'Trf_MDUpdate'. SEE ALSO
Trf_Init(3), Trf_SafeInit(3), Trf_IsInitialized(3), Trf_CreateOptions(3), Trf_DeleteOptions(3), Trf_CheckOptions(3), Trf_SetOption(3), Trf_SetObjOption(3), Trf_QueryOptions(3), Trf_SeekQueryOptions(3), Trf_WriteProc(3), Trf_CreateCtrlBlock(3), Trf_DeleteCtrlBlock(3), Trf_TransformCharacter(3), Trf_TransformBuffer(3), Trf_FlushTransformation(3), Trf_ClearCtrlBlock(3), Trf_QueryMaxRead(3), Trf_Register(3), Trf_ConverterOptions(3), Trf_MDStart(3), Trf_MDUpdate(3), Trf_MDFinal(3), Trf_MDCheck(3), Trf_RegisterMessageDigest(3), Trf_LoadLibrary(3), Trf_XorBuffer(3), Trf_ShiftRegister(3), Trf_FlipRegisterShort(3), Trf_FlipRegisterLong(3), Trf_InitStubs(3) c2man transform.h 27 August 2002 Trf_MDUpdateBuf(3)

Check Out this Related Man Page

RIPEMD(3)						   BSD Library Functions Manual 						 RIPEMD(3)

RIPEMD160_Init, RIPEMD160_Update, RIPEMD160_Final, RIPEMD160_End, RIPEMD160_File, RIPEMD160_FileChunk, RIPEMD160_Data -- calculate the RIPEMD160 message digest LIBRARY
Message Digest (MD4, MD5, etc.) Support Library (libmd, -lmd) SYNOPSIS
#include <sys/types.h> #include <ripemd.h> void RIPEMD160_Init(RIPEMD160_CTX *context); void RIPEMD160_Update(RIPEMD160_CTX *context, const unsigned char *data, unsigned int len); void RIPEMD160_Final(unsigned char digest[20], RIPEMD160_CTX *context); char * RIPEMD160_End(RIPEMD160_CTX *context, char *buf); char * RIPEMD160_File(const char *filename, char *buf); char * RIPEMD160_FileChunk(const char *filename, char *buf, off_t offset, off_t length); char * RIPEMD160_Data(const unsigned char *data, unsigned int len, char *buf); DESCRIPTION
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(). The RIPEMD160_End() function is a wrapper for RIPEMD160_Final() which converts the return value to a 41-character (including the terminating '') 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. 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. SEE ALSO
md4(3), md5(3), sha(3) HISTORY
These functions appeared in FreeBSD 4.0. AUTHORS
The core hash routines were implemented by Eric Young based on the published RIPEMD160 specification. BUGS
No method is known to exist which finds two files having the same hash value, nor to find a file with a specific hash value. There is on the other hand no guarantee that such a method does not exist. BSD
March 28, 2014 BSD
Man Page

Featured Tech Videos