Home | History | Annotate | Download | only in libtomcrypt

Lines Matching refs:Code

151 application can support all ciphers/hashes/prngs/bignum without changing the source code.
181 you have to update the associated support code as well. In LibTomCrypt the associated code (\textit{chaining modes in this case})
229 commented upon. When a function does return a CRYPT error code it can be translated into a string with
253 There is no initialization routine for the library and for the most part the code is thread safe. The only thread
351 In the above example if the size of the RSA public key was more than 1024 bytes this function would return an error code
658 the file \textit{tomcrypt\_cfg.h}. The first option is \textit{TWOFISH\_SMALL} which when defined will force the Twofish code
661 defined will force the Twofish code to use pre-computed tables for the two s-boxes $q_0, q_1$ as well as the multiplication
662 by the polynomials 5B and EF used in the MDS multiplication. As a result the code is faster and slightly larger. The
673 \hline undefined & defined & Faster key setup, larger code. \\
675 \hline defined & defined & Faster, 0.2KB of ram, larger code. \\
889 The routines return {\bf CRYPT\_OK} if the cipher initialized correctly, otherwise, they return an error code.
1072 of 16. The LRW code uses a fast tweak update such that consecutive blocks are encrypted faster than if random seeking where used.
1087 code.
1238 The EAX mode code can be tested to ensure it matches the test vectors by calling the following function:
1792 This will return {\bf CRYPT\_OK} if the hash matches the test vectors, otherwise it returns an error code. An
1943 To perform the above hash with md5 the following code could be used:
1976 work exactly like those of the cipher registration code. The functions are:
2020 data. While it is in the hash system you still have to tell the CHC code which cipher to use. This is accomplished
2078 of a message is a keyed authentication code that only the owner of a private symmetric key will be able to verify. The purpose is
2092 The \textit{hmac} parameter is the state for the HMAC code. The \textit{hash} parameter is the index into the descriptor table of the hash you want
2103 are finished with the HMAC process you must call the following function to get the HMAC code:
2110 The \textit{hmac} parameter is the HMAC state you are working with. The \textit{out} parameter is the array of octets where the HMAC code should be stored.
2111 You must set \textit{outlen} to the size of the destination buffer before calling this function. It is updated with the length of the HMAC code
2113 the HMAC code) then the HMAC code is truncated as per FIPS-198 specifications (e.g. take the first \textit{outlen} bytes).
2127 This will produce an HMAC code for the array of octets in \textit{in} of length \textit{inlen}. The index into the hash descriptor
2143 To test if the HMAC code is working there is the following function:
2148 Which returns {\bf CRYPT\_OK} if the code passes otherwise it returns an error code. Some example code for using the
2201 algorithm which produces a Message Authentication Code (MAC) using only a block cipher such as AES. Note: OMAC has been standardized as
2246 Which will terminate the OMAC and output the \textit{tag} (MAC) to \textit{out}. Note that unlike the HMAC and other code
2249 the output MAC code will only be five bytes long. If \textit{outlen} is larger than the default size it is set to the default
2252 Similar to the HMAC code
2281 To test if the OMAC code is working there is the following function:
2286 Which returns {\bf CRYPT\_OK} if the code passes otherwise it returns an error code. Some example code for using the
2339 API as the provided OMAC code.
2386 Similar to the OMAC code the file and memory functions are also provided. To PMAC a buffer of memory in one shot use the
2415 To test if the PMAC code is working there is the following function:
2420 Which returns {\bf CRYPT\_OK} if the code passes otherwise it returns an error code.
2499 As of LibTomCrypt v1.15, XCBC-MAC (RFC 3566) has been provided to support TLS encryption suites. Like OMAC, it computes a message authentication code
2577 with other ciphers. For LibTomCrypt, the F9--MAC code can use any cipher.
3169 it returns an error code.
3886 used during encryption. If the wrong key is provided the function will not specifically return an error code. It is important
3941 The signature code is an implementation of X9.62 EC--DSA, and the output is compliant for GF(p) curves.
4088 is stored and the function returns an error code. The DSA \textit{key} must be of the \textbf{PK\_PRIVATE} persuasion.
4211 The macro is relatively safe with respect to modifying variables, for instance the following code is equivalent.
4360 SET and SET OF are related to the SEQUENCE type in that they can be pretty much be decoded with the same code. However, they are different, and they should
4706 \begin{flushleft}and we decoded it with the following code:\end{flushleft}
4724 node with the following code will bring us to the \textit{Name} portion of the SEQUENCE:
4732 We can walk to this node with the following code:
4939 Also, virtually all of the functions return an error code or {\bf CRYPT\_OK}. You should detect all errors, as simple
5018 code before threads are initiated.
5020 The rest of the code uses state variables you must pass it such as hash\_state, hmac\_state, etc. This means that if each
5145 defines are explained below. You can specify multiple archives (say if you want to support two math libraries, or add on additional code) to
5223 bios code uses these macros to redirect to very compact heap and string operations.
5296 When TWOFISH\_TABLES is defined the cipher will use pre-computed (and fixed in code) tables required to work. This is
5297 useful when TWOFISH\_SMALL is defined as the table values are computed on the fly. When this is defined the code size
5311 When this is defined some of the code such as the Rijndael and SAFER+ ciphers are replaced with smaller code variants.
5312 These variants are slower but can save quite a bit of code space.
5348 to be highly portable and easy to build out of the box on pretty much any platform. As such there are no assembler inlines throughout the code, I make no assumptions
5353 the optimized code without re--writing. This also paves the way for hardware drivers that can access hardware accelerated cryptographic devices.
5745 This function is meant to perform an optimized OMAC1 (CMAC) message authentication code computation when the user calls omac\_memory().
5749 This function is meant to perform an optimized XCBC-MAC message authentication code computation when the user calls xcbc\_memory().
5753 This function is meant to perform an optimized F9 message authentication code computation when the user calls f9\_memory(). Like f9\_memory(), it requires