Home
last modified time | relevance | path

Searched refs:any (Results 1 – 25 of 38) sorted by relevance

12

/mbedtls-3.4.0/
DLICENSE31 "Object" form shall mean any form resulting from mechanical
41 "Derivative Works" shall mean any work, whether in Source or Object
49 "Contribution" shall mean any work of authorship, including
50 the original version of the Work and any modifications or additions
55 means any form of electronic, verbal, or written communication sent
63 "Contributor" shall mean Licensor and any individual or Legal Entity
83 institute patent litigation against any entity (including a
86 or contributory patent infringement, then any patent licenses
91 Work or Derivative Works thereof in any medium, with or without
95 (a) You must give any other recipients of the Work or
[all …]
DBRANCHES.md3 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.
31 modification with any later release x.y'.z' with the same major version
70 keys written under any Mbed TLS 3.x with x <= y).
86 re-compiling) and to avoid any increase in code size or RAM usage, or in the
DREADME.md74 * If not cross-compiling, running `make` with any target, or just `make`, will automatically genera…
138 - `Release`. This generates the default code without any unnecessary information in the binary fi…
272 …e communication. Second, it can also be used independently of other PSA components on any platform.
/mbedtls-3.4.0/docs/architecture/psa-migration/
Dpsa-limitations.md59 done any time.)
75 migration by implementing RFC 7919. (Implementing RFC 7919 could be done any
112 - salt length: any valid length accepted
126 - salt length can be either "standard" (<= hashlen, see note) or "any"
130 - salt length: either <= hashlen (see note), or any depending on algorithm
306 There's no question about what to do with TLS (any version); the only question
Dstrategy.md47 currently possible to compile TLS and X.509 without any of the options.
297 calling any function from these modules. This condition does not constitute a
429 It is unclear how much value, if any, a zero-cost compatibility layer that's
/mbedtls-3.4.0/docs/
Dgetting_started.md62 To use the Mbed Crypto APIs, call `psa_crypto_init()` before calling any other API. This initialize…
363 …tup()` or `psa_cipher_decrypt_setup()`, you can terminate the operation at any time by calling `ps…
365 The call to `psa_cipher_abort()` frees any resources associated with the operation, except for the …
368 …ate_iv()`, `psa_cipher_set_iv()` or `psa_cipher_update()` fails (returning any status other than `…
373 You must call `psa_cipher_abort()` at some point for any operation that is initialized successfully…
489 … you can terminate the operation at any time by calling `psa_hash_abort()`. The call to `psa_hash_…
492 1. A call to `psa_hash_update()` fails (returning any status other than `PSA_SUCCESS`).
498 You must call `psa_hash_abort()` at some point for any operation that is initialized successfully (…
D3.0-migration-guide.md78 The change affects users who use any of the following functions:
100 treated differently from any other invalid pointer, and typically leads to a
129 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 any
236 … 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 guaranteed
553 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 compression
704 Please switch to any of the modern, recommended ciphersuites (based on
[all …]
Duse-psa-crypto.md14 `psa_crypto_init()` before calling any function from the SSL/TLS, X.509 or PK
/mbedtls-3.4.0/docs/proposed/
Dpsa-driver-interface.md29 …ple drivers from different providers into the same implementation, without any prior arrangement o…
35any platform-specific consideration. Driver calls are simple C function calls. Interactions with p…
63 In addition to the properties described here, any JSON object may have a property called `"_comment…
127 …nistic ECDSA signatures (but not signature verification) using any hash algorithm and any curve th…
241 …this fails, the core destroys the operation context object without calling any other driver entry …
243any entry point fails, the core calls the driver's `xxx_abort` entry point for this operation fami…
244 …oint fails, the core destroys the operation context object without calling any other driver entry …
256 …n context byte by byte, therefore hash operation contexts must not contain any embedded pointers (…
432 …itialization of the PSA Cryptography subsystem. If the init entry point of any driver fails, the i…
438 The init entry point does not take any parameter.
[all …]
Dpsa-conditional-inclusion-c.md71 … feature is available through the PSA API. These symbols should be used in any place that requires…
97 Rationale: Finite-field Diffie-Hellman code is usually not specialized for any particular group, so…
166 Since configuration symbols must be undefined or 1, any other value should trigger an `#error`.
194 …nism proposed here. The approximation considers a feature to be enabled if any part of it is enabl…
/mbedtls-3.4.0/tests/suites/
Dtest_suite_random.data38 # with something larger than any RNG call made by Mbed TLS itself expects.
Dhelpers.function81 * If any slots are in use, mark the current test as failed.
Dtest_suite_psa_crypto_metadata.data209 Asymmetric signature: RSA PSS-any-salt SHA-256
245 Asymmetric signature: RSA PSS-any-salt with wildcard hash
Dtest_suite_psa_crypto_driver_wrappers.data121 verify_hash transparent driver: in driver Public Key RSA-1024 PSS-any-salt SHA-256
125 verify_hash transparent driver: fallback Public Key RSA-1024 PSS-any-salt SHA-256
129 verify_hash transparent driver: error Public Key RSA-1024 PSS-any-salt SHA-256
225 verify_message transparent driver: calculate in driver Public Key RSA PSS-any-salt SHA-256
229 verify_message transparent driver: fallback Public Key RSA PSS-any-salt SHA-256
233 verify_message transparent driver: error Public Key RSA PSS-any-salt SHA-256
Dmain_test.function127 * parameter array and do not perform any error detection.
Dtest_suite_psa_crypto.data915 PSA key policy: asymmetric signature, wrong alg family (PSS std/any salt)
919 PSA key policy: asymmetric signature, wrong alg family (PSS any/std salt)
967 PSA key policy: msg asymmetric signature, wrong alg family (PSS std/any salt)
971 PSA key policy: msg asymmetric signature, wrong alg family (PSS any/std salt)
1174 Copy key: source=ECDSA(any)+ECDH, target=ECDSA(SHA256)+ECDH
1178 Copy key: source=ECDH+ECDSA(any), target=ECDH+ECDSA(SHA256)
1270 Copy key: source=ECDSA(any)+ECDH, target=ECDSA(SHA256)+ECDH, opaque
1274 Copy key: source=ECDH+ECDSA(any), target=ECDH+ECDSA(SHA256), opaque
4072 PSA signature size: RSA keypair, 1024 bits, PSS-any-salt
4092 PSA import/exercise RSA keypair, PSS-any-salt-SHA-256
[all …]
Dtest_suite_ssl.function698 * \retval MBEDTLS_TEST_ERROR_CONTEXT_ERROR, if any of the needed context
703 * This function will also return any error from
735 * \retval MBEDTLS_TEST_ERROR_CONTEXT_ERROR, if any of the needed context
739 * This function will also return any error other than
2874 /* The result depends on whether any data was sent */
3013 /* The result depends on whether any data was sent */
4202 * sure our padding checking code does not perform any out-of-bounds reads
4955 /* Allocate exact size so that asan/valgrind can detect any overwrite */
5009 /* Allocate exact size so that asan/valgrind can detect any overread */
5066 /* Without any modification, we should be able to successfully
/mbedtls-3.4.0/scripts/
Dconfig.py83 def any(self, *names): member in Config
85 return any(self.__contains__(name) for name in names)
/mbedtls-3.4.0/docs/architecture/
Dtls13-support.md104 there is rarely any need to modify the configuration from that used for
156 exchange mode enabled, the TLS 1.3 implementation does not contain any code
161 mode enabled, the TLS 1.3 implementation does not contain any code related
170 exchange mode enabled, the TLS 1.3 implementation does not contain any code
444 * parsing stage: parse the message and restrict as much as possible any
468 * writing stage: write the message and restrict as much as possible any update
Dpsa-crypto-implementation-structure.md22 … 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…
Dmbed-crypto-storage-specification.md33 We do not make any promises regarding key storage, or regarding the nonvolatile random seed file on…
66 The file format is just the seed as a byte string with no metadata or encoding of any kind.
125 The file format is just the seed as a byte string with no metadata or encoding of any kind.
/mbedtls-3.4.0/docs/architecture/testing/
Ddriver-interface-test-strategy.md79 * 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 …
Dinvasive-testing.md49 > # and not expected to be raised any time soon) is less than the maximum
69 …In such cases, the function should generally not modify its parameters, so any pointer argument sh…
280 …ecause the danger is that the compiler optimizes the zeroization away, and any C code that observe…
288 …f. Use the cleanup code (after the `exit` label in test functions) to free any memory that the fun…
/mbedtls-3.4.0/programs/fuzz/
DREADME.md24 And you can run any of the fuzz targets like `fuzz_client`.
/mbedtls-3.4.0/programs/
DREADME.md20 * [`pkey/gen_key.c`](pkey/gen_key.c): generates a key for any of the supported public-key algorithm…

12