Lines Matching full:and
16 security and technicalities of each cryptographic primitive are found in the
35 * Requires: SHA-256 and HMAC-SHA256.
91 respect to other metrics and countermeasures for particular threats. These
92 peculiarities would increase the code size and thus are not considered here.
95 that it is unnecessary to build and allocate object code for more primitives
97 one can select and compile only the primitives required by the application.
106 in order to meet its design goals (in special, minimal code size) and to better
151 step: entropy seed, personalization and a nonce (which is not implemented).
152 TinyCrypt requires the personalization byte array and automatically creates
160 twice the size as for AES-128, and the key schedule is 40% larger.
177 * TinyCrypt CBC decryption assumes that the iv and the ciphertext are
188 tags (e.g. 2^64) to finally be able to look for collisions and benefit
197 of CCM under a given key and the maximum payload length for those
214 accepts any even integer between 4 and 16, as suggested in SP 800-38C.
217 0 and (2^16 - 2^8) = 65280 bytes.
221 * Both non-empty payload and associated data (it encrypts and
222 authenticates the payload and only authenticates the associated data);
224 * Non-empty payload and empty associated data (it encrypts and
227 * Non-empty associated data and empty payload (it degenerates to an
236 * ECC-DH and ECC-DSA:
245 first. You can use the 'ecc_bytes2native()' and 'ecc_native2bytes()'
246 functions to convert between the native integer representation and the
262 * Measurement of code, data structures, and other digital artifacts (SHA256);
272 * Construct nonces and challenges (HMAC-PRNG, CTR-PRNG);
297 For the case of the EC-DH and EC-DSA implementations, most of the test vectors
319 * `NIST SP 800-38A (AES-CBC and AES-CTR)`_
321 .. _NIST SP 800-38A (AES-CBC and AES-CTR):
349 * `RFC 6090 (ECC-DH and ECC-DSA)`_
351 .. _RFC 6090 (ECC-DH and ECC-DSA):