Searched refs:any (Results 1 – 25 of 50) sorted by relevance
12
38 "Object" form shall mean any form resulting from mechanical48 "Derivative Works" shall mean any work, whether in Source or Object56 "Contribution" shall mean any work of authorship, including57 the original version of the Work and any modifications or additions62 means any form of electronic, verbal, or written communication sent70 "Contributor" shall mean Licensor and any individual or Legal Entity90 institute patent litigation against any entity (including a93 or contributory patent infringement, then any patent licenses98 Work or Derivative Works thereof in any medium, with or without102 (a) You must give any other recipients of the Work or[all …]
3 At any point in time, we have a number of maintained branches, currently consisting of:18 These branches will not receive any changes or updates.36 modification with any later release x.y'.z' with the same major version75 keys written under any Mbed TLS 3.x with x <= y).91 re-compiling) and to avoid any increase in code size or RAM usage, or in the
82 Mbed TLS doesn't make any security guarantees against local non-timing-based91 Mbed TLS doesn't make any security guarantees against local fault injection101 Mbed TLS doesn't make any security guarantees against physical attacks. If
15 `psa_crypto_init()` before calling any function from the SSL/TLS, X.509 or PK17 at any time.30 `psa_crypto_init()` before you call any other `psa_xxx()` function. Other38 calling any function from PK, X.509 or TLS; however it doesn't change anything57 longer beta, and production quality, so there's no longer any reason to make63 before calling any PK, X.509 or TLS functions. For the same compatibility
45 make sure you call `psa_crypto_init()` before any function that uses the46 driver-only mechanisms. Note that this is already a requirement for any use of88 You need to call `psa_crypto_init()` before any crypto operation that uses165 A limited subset of `ecp.c` will still be automatically re-enabled if any of174 Note: when any of the above options is enabled, a subset of `ecp.c` will
78 The change affects users who use any of the following functions:100 treated differently from any other invalid pointer, and typically leads to a129 doesn't have any entropy source, you should use `MBEDTLS_ENTROPY_NV_SEED`152 Please use the new names directly in your code; `scripts/rename.pl` (from any236 … or using GCM via the `mbedtls_cipher_xxx` or `psa_aead_xxx` interfaces do not require any changes.552 `certs.c` is out of the library there is no longer any stability guaranteed553 and it may change in incompatible ways at any time.578 extension if it contains any unsupported certificate policies.692 cause any failures however if you used to enable TLS record-level compression704 Please switch to any of the modern, recommended ciphersuites (based on[all …]
22 …er. Using flags set at compile time, the driver wrapper ascertains whether any present drivers sup…68 Include any header files required by the driver in `psa_crypto_driver_wrappers.h`, placing the `#in…137 …ntly different to the default. Define the macro for the driver, along with any other custom config…
9 * There aren't any yet at the time of writing.)28 void printf_int(char *format, /* any format expecting one int argument, e.g. "%d" */
38 # with something larger than any RNG call made by Mbed TLS itself expects.
64 /* Change any one byte of the plaintext or MAC. The MAC will be wrong. */273 * sure our padding checking code does not perform any out-of-bounds reads
121 verify_hash transparent driver: in driver Public Key RSA-1024 PSS-any-salt SHA-256125 verify_hash transparent driver: fallback Public Key RSA-1024 PSS-any-salt SHA-256129 verify_hash transparent driver: error Public Key RSA-1024 PSS-any-salt SHA-256225 verify_message transparent driver: calculate in driver Public Key RSA PSS-any-salt SHA-256229 verify_message transparent driver: fallback Public Key RSA PSS-any-salt SHA-256233 verify_message transparent driver: error Public Key RSA PSS-any-salt SHA-256
229 Asymmetric signature: RSA PSS-any-salt SHA-256265 Asymmetric signature: RSA PSS-any-salt with wildcard hash
66 done any time.)82 migration by implementing RFC 7919. (Implementing RFC 7919 could be done any123 - salt length: any valid length accepted137 - salt length can be either "standard" (<= hashlen, see note) or "any"141 - salt length: either <= hashlen (see note), or any depending on algorithm317 There's no question about what to do with TLS (any version); the only question
171 if any(x in ffdh_groups for x in self._named_groups):370 if any(x in ec_groups for x in self._named_groups):373 if any(x in ffdh_groups for x in self._named_groups):
18 # everest is not directly linked against any mbedtls targets
16 # p256m is not directly linked against any mbedtls targets
15 …lication calls an API function, as far as the application is concerned, at any given point in time…40 …le-storage). We do not need to take any special precautions in the library design, and we do not n…141 * Aborting means removing any trace of the key creation.144 …* Aborting means destroying the key in the secure element and removing any local storage used for …146 …ld have been done if the transaction had not been interrupted, by removing any remaining local sto…149 …ld have been done if the transaction had not been interrupted, by removing any remaining local sto…157 …ot require querying the state of the secure element. This does not require any special precautions…211 …e point where the key has been added to the transaction list, and ignoring any failure of a remova…236 …e point where the key has been added to the transaction list, and ignoring any failure of a remova…295 …itself an operation that must respect the invariant, and so we do not need any special testing for…[all …]
98 there is rarely any need to modify the configuration from that used for150 exchange mode enabled, the TLS 1.3 implementation does not contain any code155 mode enabled, the TLS 1.3 implementation does not contain any code related164 exchange mode enabled, the TLS 1.3 implementation does not contain any code438 * parsing stage: parse the message and restrict as much as possible any462 * writing stage: write the message and restrict as much as possible any update
10 …Mbed TLS releases without proper concurrency management: 3.0.0, 3.1.0, and any other subsequent 3.…54 * At most one driver entry point is active at any given time.58 * By default, each driver only has at most one entry point active at any given time. In other words…263 * READING: any thread may read from the slot.272 * `psa_wipe_key_slot`: any → UNUSED. If the slot is READING or WRITING on entry, this function must…
22 … in the PSA Cryptography API specification but does not perform on its own any cryptographic opera…66 In case of any error occurring at step 3 or 4, psa_fail_key_creation() is called. It wipes and clea…135 …B2, B3, ...} but there is no particular reason why enabling A would enable any of the specific Bi'…
72 def any(self, *names): member in Config74 return any(self.__contains__(name) for name in names)
31 …ple drivers from different providers into the same implementation, without any prior arrangement o…37 …any platform-specific consideration. Driver calls are simple C function calls. Interactions with p…65 In addition to the properties described here, any JSON object may have a property called `"_comment…129 …nistic ECDSA signatures (but not signature verification) using any hash algorithm and any curve th…243 …this fails, the core destroys the operation context object without calling any other driver entry …245 …any entry point fails, the core calls the driver's `xxx_abort` entry point for this operation fami…246 …oint fails, the core destroys the operation context object without calling any other driver entry …258 …n context byte by byte, therefore hash operation contexts must not contain any embedded pointers (…445 …capacity limitation and must return `PSA_ERROR_INSUFFICIENT_CAPACITY` from any output request that…451 `capacity` is guaranteed to be less or equal to any value previously set through this entry point, …[all …]
71 … feature is available through the PSA API. These symbols should be used in any place that requires…86 … key of that type for enabled algorithms. This is automatically enabled if any of the other `PSA_W…106 Rationale: Finite-field Diffie-Hellman code is usually not specialized for any particular group, so…175 Since configuration symbols must be undefined or 1, any other value should trigger an `#error`.203 …nism proposed here. The approximation considers a feature to be enabled if any part of it is enabl…
79 * Test that `psa_destroy_key()` does not leave any trace of the key.83 …</sub>, ..., M<sub>n</sub>). If the operation is interrupted by a reset at any point, it must be e…90 …done by e.g. using a key that is supposed to be present) and does not have any unexpected content …
24 And you can run any of the fuzz targets like `fuzz_client`.
