Searched refs:read (Results 1 – 25 of 53) sorted by relevance
123
3 read lifetime: (DEFAULT,LOCAL_STORAGE)7 read lifetime: (READ_ONLY,LOCAL_STORAGE)11 read lifetime: (2,LOCAL_STORAGE)15 read lifetime: (254,LOCAL_STORAGE)19 read lifetime: PERSISTENT23 read usage without implication: 027 read usage without implication: COPY31 read usage without implication: DECRYPT35 read usage without implication: DERIVE39 read usage without implication: ENCRYPT[all …]
63 /* Make a 16/32/64 byte read from the aligned location, and copy to expected */256 uint64_t read = 0;260 read = MBEDTLS_GET_UINT16_BE(x, offset);263 read = MBEDTLS_GET_UINT24_BE(x, offset);266 read = MBEDTLS_GET_UINT32_BE(x, offset);269 read = MBEDTLS_GET_UINT64_BE(x, offset);275 read = MBEDTLS_GET_UINT16_LE(x, offset);278 read = MBEDTLS_GET_UINT24_LE(x, offset);281 read = MBEDTLS_GET_UINT32_LE(x, offset);284 read = MBEDTLS_GET_UINT64_LE(x, offset);[all …]
22 PEM read (unencrypted, valid)25 PEM read (unencrypted, empty content)28 PEM read (DES-EDE3-CBC + invalid iv)32 PEM read (DES-CBC + invalid iv)36 PEM read (AES-128-CBC + invalid iv)40 PEM read (unknown encryption algorithm)44 PEM read (malformed PEM DES-CBC)48 PEM read (malformed PEM DES-EDE3-CBC)52 PEM read (malformed PEM AES-128-CBC)58 # length read from the decoded ASN.1 data (i.e. extra padding, if any, is ignored).[all …]
224 ECP read binary #1 (zero, invalid ilen)228 ECP read binary #2 (zero, invalid first byte)232 ECP read binary #3 (zero, OK)236 ECP read binary #4 (non-zero, invalid ilen, too short)240 ECP read binary #4a (non-zero, invalid ilen, too short)244 ECP read binary #4b (non-zero, invalid ilen, too short)248 ECP read binary #4c (non-zero, invalid ilen, too long)252 ECP read binary #4d (non-zero, invalid ilen, too long)256 ECP read binary #4e (non-zero, invalid ilen, too long)260 ECP read binary #5 (non-zero, invalid first byte)[all …]
94 int read = 0xdeadbeef;95 TEST_EQUAL(mbedtls_asn1_get_bool(&data.p, data.end, &read), 0);96 TEST_EQUAL(val, read);122 int read = 0xdeadbeef;123 TEST_EQUAL(mbedtls_asn1_get_int(&data.p, data.end, &read), 0);124 TEST_EQUAL(val, read);151 int read = 0xdeadbeef;152 TEST_EQUAL(mbedtls_asn1_get_enum(&data.p, data.end, &read), 0);153 TEST_EQUAL(val, read);167 mbedtls_mpi mpi, read;[all …]
53 ECDSA write-read hash zero #157 ECDSA write-read hash zero #261 ECDSA write-read hash zero #365 ECDSA write-read hash zero #469 ECDSA write-read hash zero #573 ECDSA write-read random #177 ECDSA write-read random #281 ECDSA write-read random #385 ECDSA write-read random #489 ECDSA write-read random #5[all …]
66 * NV seed read/write functions that use a buffer instead of a file93 * NV seed read/write helpers that fill the base seedfile439 /* Check if platform NV read and write manipulate the same data */448 /* Check if platform NV write and raw read manipulate the same data */489 // Make sure we read/write NV seed from our buffers502 // Set the initial NV seed to read
166 size_t i, j, written, read;227 written = read = 0;233 output + read, get[j]));234 read += get_ret[j];235 TEST_ASSERT(read <= written);237 TEST_ASSERT(memcmp(output + read - get_ret[j],238 input + read - get_ret[j], get_ret[j])299 size_t written, read;329 written = read = 0;347 recv_ret = recv(&server, received + read, MSGLEN - read);[all …]
229 * will still be able to read it. */255 * can read back what this version wrote. */272 /* Backward compatibility: read a key in the format of a past version
235 /* This test exercises the behaviour of the MPS reader when a read request271 * in the situation where a read request goes beyond the bounds of the272 * current read buffer, _and_ the reader's accumulator is too small to364 * sufficient to fulfill the original read request.365 * - The consumer retries the original read request, which689 * - A read request via `mbedtls_mps_reader_get()` can't990 * producer until the original read request can be fulfilled.994 * The reader does not guarantee that inconsistent read requests
234 # not attempt to read invalidly outside the buffer.240 # not attempt to read invalidly outside the buffer.250 # LMS type to 0x7, and imports it. This should fail, and not attempt to read261 # LMOTS type to 0x5, and imports it. This should fail, and not attempt to read
5 PSA storage read: AES-GCM+CTR
126 # not attempt to read invalidly outside the buffer.136 # LMOTS type to 0x5, and imports it. This should fail, and not attempt to read
37 #### Read-read inconsistency39 If an input argument is in shared memory, there is a risk of a **read-read inconsistency**:45 …eld in the shared memory between the two reads and thus cause a buffer overread on the second read.52 #### Write-read inconsistency54 If an output argument is in shared memory, there is a risk of a **write-read inconsistency**:74 …ation, which re-shares it with the crypto service. A malicious client can read another client (the…76 #### Write-read feedback102 …memory cannot result in a security violation other than [write-read feedback](#write-read-feedback…104 * Never read the same input twice at the same index.105 * Never read back from an output.[all …]
6 …ot exhaustive. Please consult the documentation of individual modules and read the library header …47 …read access is necessary: the field can be `const`, and modifications to it do not need to be supp…
227 - the macros to read from memory a multi-byte integer in big-endian order241 check that we do not write or read past the end of a data buffer. The243 to read/write past the end of a data buffer.259 - When an TLS 1.3 structure is written or read by a function or as part of
50 content = open(CHECK_GENERATED_FILES, encoding="utf-8").read()58 content = open(filename, encoding="utf-8").read()
241 whole_file = input_stream.read()258 input_stream.read(), False)
5 …des a persistent key store. It is possible to create a persistent key and read it back later. This…15 …ting is: as a user of Mbed TLS, I want to store a key under version V and read it back under versi…27 …tate that V would have produced. Thus, this approach validates that W can read storage states crea…29 …ck passing on version W with the same data that proves that version W can read back what version V…
128 * Check the format of files (which matters so that the product can still read old files after an up…228 …st-specific conditional compilation littered through the code, as that makes the code hard to read.248 … a test that the product isn't capable of doing, we can use a debugger to read or modify the memor…332 #### Storage read failure334 Goal: test the robustness against read errors.
149 Mbed TLS provides the mbedtls_ssl_read_early_data() API to read the early data155 MBEDTLS_ERR_SSL_RECEIVED_EARLY_DATA error code. Early data can then be read
221 if f.read(1) != b"\n":236 if f.read().startswith(codecs.BOM_UTF8):
271 old_content = open(file_name, encoding='utf-8').read()
56 #define read(fd, buf, len) recv(fd, (char *) (buf), (int) (len), 0) macro550 ret = (int) read(fd, buf, len); in mbedtls_net_recv()
75 of Mbed TLS (for example, all Mbed TLS 3.y versions will be able to read78 Mbed TLS 3.x can also read keys written by Mbed TLS 2.25.0 through 2.28.x
