Lines Matching refs:Most
226 In general the API is very simple to memorize and use. Most of the functions return either {\bf void} or {\bf int}. Functions
253 There is no initialization routine for the library and for the most part the code is thread safe. The only thread
355 As of v1.13, most functions will update your length on failure to indicate the size required by the function. Not all functions
392 Most functions require inputs that are arrays of the data type \textit{unsigned char}. Whether it is a symmetric key, IV
553 The number of rounds of most ciphers is not an option you can change. Only RC5 allows you to change the number of
649 Rijndael as it makes the most sense for this cipher.
730 as there is no more room (it can have 32 ciphers at most) it will return {\bf{-1}}. If you try to add the same cipher more
1764 Essentially all hash messages are virtually infinitely\footnote{Most hashes are limited to $2^{64}$ bits or 2,305,843,009,213,693,952 bytes.} long message which
2864 \textit{Note:} This PRNG is still secure for most tasks but is no longer recommended. Users
2871 to work with most cipher and hash combos based on which you have chosen to build into the library.} while
2973 on most *NIX platforms provides cryptographic random bits\footnote{This device is available in Windows through the Cygwin compiler suite. It emulates \textit{/dev/random} via the Microsoft CSP.}.
3244 The most often suggested value for $e$ is $65537$ since it is large enough to make such attacks impossible and also well
3658 to 4096 bits (512 bytes) which is way more than what is required by ECC. At most, you need 1152 bits to accommodate ECC--521. If you're only using (say)
4896 In the event that a composite did make it through it would most likely cause the the algorithm trying to use it to fail. For
4925 Probably the single most vulnerable point of any cryptosystem is the PRNG. Without one, generating and protecting secrets
4954 For symmetric ciphers, use as large as of a key as possible. For the most part \textit{bits are cheap} so using a 256--bit key
5044 All GNU driven makefiles (including the makefile for ICC) use a set of common variables to control the build and install process. Most of the
5287 build to the most minimum of useful functionality.
5347 require updating. This has the nice benefit that one can add ciphers (etc.) not have to re--write portions of the API. For the most part, LibTomCrypt has also been written
5351 That works well for most cases but there are times where performance is of the essence. This API allows optimized routines to be dropped in--place of the existing
5357 development simple. In most dependent routines all an end developer has to do is register\_XXX() the descriptor and they are set.
6392 Most of the functions are fairly straightforward and do not need documentation. We'll cover the basic conventions of the API and then explain the accelerated functions.
