Searched refs:known (Results 1 – 25 of 29) sorted by relevance
12
131 * cycle through all known transparent accelerators */171 /* Key is declared with a lifetime not known to us */205 * cycle through all known transparent accelerators */243 /* Key is declared with a lifetime not known to us */292 * cycle through all known transparent accelerators */356 /* Key is declared with a lifetime not known to us */396 * cycle through all known transparent accelerators */457 /* Key is declared with a lifetime not known to us */526 * cycle through all known transparent accelerators */549 /* Key is declared with a lifetime not known to us */[all …]
85 * The key is declared with a lifetime not known to us.166 * cycle through all known transparent accelerators */187 /* Key is declared with a lifetime not known to us */
3 # known from most languages
5 # Use a known version of Pylint, because new versions tend to add warnings
76 def known(self, name): member in Config
36 /* Populate with known data */250 /* Populate with known data: x == { 0, 1, 2, ... } */
358 /* This is a known-answer test, and although tests use a mock entropy
1072 /* Prepare an RNG with known output, limited to rng_bytes. */1092 * with known output, so check that the output contains the
754 TEST_FAIL("No known verify callback selected");
884 // Load curve info and compare with known values
2601 # The parse_path tests are known to fail when compiled for a 32-bit architecture2602 # and run via qemu-user on Linux on a 64-bit host. This is due to a known
6848 * 1. Test interruptible sign hash with known outcomes (deterministic ECDSA7444 * 1. Test interruptible verify hash with known outcomes (deterministic ECDSA
61 # Note: openssl-1.0.2 and earlier has known build issues with parallel make.
121 3. The code of the PSA Crypto dispatch layer (also known as the core), which is provided by Mbed TL…138 It is ok to skip the copy if it is known for sure that a buffer is not in shared memory. However, t…157 Note that in this context, a “small buffer” is one with a size limit that is known at compile time,…178 …it (which can easily be checked before emitting any data, since the data size is known in advance).198 …t arbitrary overlap, although this is not always the case in Mbed TLS, a [known issue](https://git…202 …at which point the dispatch layer shall copy the input for modes that are not known to be low-risk.208 …atch layer shall copy the input for algorithms such as PureEdDSA that are not known to be low-risk.
45 …(although they would normally be `struct` types). This section lists some known limitations where …
67 …a transaction across system boundaries is a well-known problem in database management, with a well…334 … the state of `id` in the internal storage nor the state of the key in the secure element is known.
152 The size of operation structures needs to be known at compile time, since callers may allocate them…
380 message. The latter occurs when it is not known what the next handshake message
27 …s under version W ≥ V, it creates and reads back a storage state which is known to be identical to…
45 well-known parameters (some of them defined in the spec, but implementations
569 ### Internal "block cipher" abstraction (previously known as "Cipher light")
155 Keys are stored internally in a global array of key slots known as the "key store", defined in `lib…180 …X` functions, read from the slot, then call `psa_unregister_read` to make known that they have fin…
260 working; there are known issues in PK, and X.509 and TLS are untested.
1020 …1.1) deprecates it in TLS, and it is very rarely used, although it is not known to be weak at the …
921 …interface is suitable both for PRNG (pseudo-random number generator, also known as DRBG (determini…
