Lines Matching refs:bignum
146 With this library all core functions (ciphers, hashes, prngs, and bignum) have the same prototype definition. They all load
151 application can support all ciphers/hashes/prngs/bignum without changing the source code.
166 pseudo--random number generators (PRNG), and bignum math routines are all used within the API through \textit{descriptor} tables which
3292 This will load the bignum from \textit{in} as a big endian integer in the format PKCS \#1 specifies, raises it to either \textit{e} or \textit{d} and stores the result
4443 These will encode or decode a signed INTEGER data type using the bignum data type to store the large INTEGER. To encode smaller values without allocating
4444 a bignum to store the value, the \textit{short} INTEGER functions were made available.
4949 need a PRNG can instantly take advantage of it. The same applies for ciphers, hashes, and bignum math routines.
5346 The entire API was designed with plug and play in mind at the low level. That is you can swap out any cipher, hash, PRNG or bignum library and the dependent API will not
5356 to functions that do the required work. For a given class of operation (e.g. cipher, hash, prng, bignum) the functions of a descriptor have identical prototypes which makes
5964 \mysection{BigNum Math Descriptors}
5965 The library also makes use of the math descriptors to access math functions. While bignum math libraries usually differ in implementation
5980 /** initialize a bignum
6396 All \textit{bignums} are accessed through an opaque \textit{void *} data type. You must internally cast the pointer if you need to access members of your bignum structure. During
6398 free the bignum as well as the structure you allocated to place it in.