Searched refs:not (Results 1 – 25 of 167) sorted by relevance

1234567

/mbedtls/tests/suites/
A D	test_suite_psa_crypto_not_supported.generated.data	3 PSA import AES 128-bit not supported 7 PSA generate AES 128-bit not supported 11 PSA import AES 192-bit not supported 15 PSA generate AES 192-bit not supported 19 PSA import AES 256-bit not supported 23 PSA generate AES 256-bit not supported 27 PSA import ARIA 128-bit not supported 35 PSA import ARIA 192-bit not supported 43 PSA import ARIA 256-bit not supported 83 PSA import DES 64-bit not supported [all …]
A D	helpers.function	39 #define KEY_VALUE_MAPPING_NOT_FOUND -1 /* Integer expression not found */ 40 #define DEPENDENCY_NOT_SUPPORTED -2 /* Dependency not supported */ 41 #define DISPATCH_TEST_FN_NOT_FOUND -3 /* Test function not found */ 46 #define DISPATCH_UNSUPPORTED_SUITE -5 /* Test suite not supported by the
A D	test_suite_psa_crypto_persistent_key.data	87 import/export persistent raw key file not exist: 1 byte 90 import/export persistent key RSA public key file not exist: 1024-bit 94 import/export persistent key RSA keypair file not exist: 1024-bit 113 import/export persistent raw key file not exist with restart: 1 byte 116 import/export persistent key RSA public key file not exist with restart: 1024-bit 120 import/export persistent key RSA keypair file not exist with restart: 1024-bit
A D	main_test.function	31 * enabled but the corresponding warnings are not treated as errors. 125 * parameter array and do not perform any error detection. 155 * DISPATCH_TEST_FN_NOT_FOUND if not found 156 * DISPATCH_UNSUPPORTED_SUITE if not compile time enabled. 193 * DISPATCH_TEST_FN_NOT_FOUND if not found 194 * DISPATCH_UNSUPPORTED_SUITE if not compile time enabled. 249 * not desirable and should be fixed later.
/mbedtls/tests/scripts/
A D	test_zeroize.gdb	9 # function in platform_util.h is not being optimized out by the compiler. To do 15 # The mbedtls_platform_zeroize() test is debugger driven because there does not 22 # data structure to remove redundant code that does not have an impact on the 25 # memory that is not accessed later in the program, so removing the call to 26 # mbedtls_platform_zeroize() does not have an observable behavior. However, 28 # the block of memory was correctly zeroed would force the compiler to not 29 # eliminate the mbedtls_platform_zeroize() call. If this does not occur, then 50 echo The buffer at was not zeroized\n 60 echo The program did not terminate correctly\n
A D	all.sh	720 not () { function 2951 not grep mxz library/ecp.o 3581 not grep mbedtls_rsa library/rsa.o 3691 not grep mbedtls_md5 library/md5.o 3768 not grep mbedtls_md5 library/md5.o 3954 not grep mbedtls_ccm library/ccm.o 3955 not grep mbedtls_gcm library/gcm.o 4023 not grep mbedtls_des library/des.o 4024 not grep mbedtls_aes library/aes.o 5803 not grep __aeabi_lmul library/*.o [all …]
/mbedtls/docs/architecture/testing/
A D	invasive-testing.md	9 This is a test strategy document, not a test plan. A description of exactly what is tested is out o… 34 …eader files from `library/`. Do not define non-public interfaces in public headers. In contrast, s… 49 > # and not expected to be raised any time soon) is less than the maximum 86 …ant to test the actual product, not a modified version, since conclusions drawn from a test of a m… 151 | Coverage | ~ Many useful tests are not reasonably achievable | 166 | Coverage | ~ Many useful tests are not reasonably achievable | 180 …not be hidden at link time (but link-time hiding is not something we currently do). Another limita… 185 | Correctness | + Does not require a product change | 225 * **Merely enabling the compile-time option should not change the behavior.**<br> 240 | Correctness | + Instrumentation generally does not affect the program's functional behavior | [all …]
A D	driver-interface-test-strategy.md	42 * Make at least one test with a key that is not in a secure element that checks that the driver met… 43 * Make at least one test with a key in a secure element with a driver that does not have the requis… 44 * Make at least one test with a key in a secure element with a driver that does not have the substr… 45 …key in each driver and check that the expected driver is called. This does not need to be done for… 55 …at are invalid and must not reach the driver, call the API function with such parameters and verif… 56 …t from the expected inputs (as is often the case for cryptographic material, but not for metadata). 79 * Test that `psa_destroy_key()` does not leave any trace of the key. 90 …s can be done by e.g. using a key that is supposed to be present) and does not have any unexpected… 102 * Run the full driver validation test suite (which does not yet exist). 113 * Run the full driver validation test suite (which does not yet exist). [all …]
/mbedtls/docs/architecture/
A D	psa-storage-resilience.md	26 * `remove()` removes a file (returning a specific error code if the file does not exist). 139 * Key creation, key not present in the secure element: 145 * Key destruction, key not present in the secure element: 238 1. Load the driver key identifier from the key file. If the key file does not exist, skip to step 4. 266 …cation, there may or may not be a restart, and after that different state modifications may occur,… 313 …d` does not exist, then no resources corresponding to that key are in a secure element. This holds… 331 * If `id` is not in the transaction list and the file `id` does not exist, then no resources corres… 378 …d` does not exist, then no resources corresponding to that key are in a secure element. This holds… 399 1. Load the current list from the transaction list if it exists and it is not already cached in mem… 405 1. Load the current list if it is not already cached in memory. It is an error if the file does not… [all …]
A D	tls13-support.md	95 Most of the Mbed TLS SSL/TLS related options are not supported or not 241 check that we do not write or read past the end of a data buffer. The 265 - We prefer grouping "related statement lines" by not adding blank lines 291 the pointer name not appended to the pointer type: 299 - string literals can extend beyond 80 characters as we do not want to 352 result in too many checks of whether something needs to be done or not in a 355 bypassed if the handshake is based on a pre-shared key and thus does not 371 data are flushed before to call the next handler. That way, handlers do not 383 reading to not modify the SSL context as this stage may be repeated if the 384 next handshake message has not been received yet. [all …]
A D	psa-shared-memory.md	58 …s the calculation, leading to an outcome that would not be possible if the intermediate data had n… 138 …not in shared memory. However, the location of the buffer is not under the control of Mbed TLS. Th… 152 … **small buffers**, the cost of copying is low. For many of those, the risk of not copying is high: 157 …l enough that copying the data is not prohibitive. For example, an RSA key fits in a small buffer.… 162 …* Note that this does not include inputs or outputs that are not processed by an asymmetric primit… 186 …yption is at risk of [write-write disclosure](#write-write-disclosure) when the tag does not match. 216 * The core (dispatch layer) shall make a copy of the following buffers, so that drivers do not rece… 246 …aviour is preserved by all major compilers then assume that compiler optimization is not a problem. 259 * Any complexity needed to prevent the compiler optimizing copies away does not have to be duplicat… 371 * Does not require complex linking against different versions of `malloc()` (as is the case with th… [all …]
A D	alternative-implementations.md	6 This document is an overview. It is not exhaustive. Please consult the documentation of individual … 22 …working, the `net_sockets` module does not currently support alternative implementations. If this … 30 …not all operations support drivers yet. The configuration option `MBEDTLS_USE_PSA_CRYPTO` causes p… 47 …not need to be at the same position in the structure. Furthermore, unless otherwise indicated, onl… 64 …context or to a part of a context does not remain valid across function calls. Alternative impleme… 72 …onding option is enabled, the built-in implementation of the function will not be compiled, and yo… 89 Merely enabling `MBEDTLS_PLATFORM_XXX_ALT` does not change the behavior: by default, `mbedtls_xxx` …
/mbedtls/.github/
A D	pull_request_template.md	9 Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new … 11 - [ ] **changelog** provided, or not required 12 - [ ] **backport** done, or not required 13 - [ ] **tests** provided, or not required 26 - please do not force-push to update your PR - just add new commit(s)
/mbedtls/docs/architecture/psa-thread-safety/
A D	psa-thread-safety.md	3 Currently, PSA Crypto API calls in Mbed TLS releases are not thread-safe. 45 We do not test or support calling other PSA API functions concurrently. 59 > * A call to `psa_destroy_key()` must not overlap with a concurrent call to any of the following f… 63 > * Concurrent calls must not use the same operation object. 67 …not apply to errors that arise from resource failures or limitations. For example, errors resultin… 72 > * Both calls can fail with error codes that are not `PSA_ERROR_ALREADY_EXISTS`. 194 …not currently loaded into slots is our abstraction function for the key store, any key not in this… 249 …at one shot operations and multi-part operations are not yet considered thread-safe, as we have no… 269 Since we do not run every cryptographic operation concurrently, we do not test that operations are … 306 `psa_destroy_key` does not block indefinitely, and when `psa_destroy_key` returns: [all …]
/mbedtls/
A D	LICENSE	35 including but not limited to software source code, documentation 40 not limited to compiled object code, generated documentation, 111 excluding those notices that do not pertain to any part of 200 you may not use this file except in compliance with the License. 221 of this license document, but changing it is not allowed. 235 When we speak of free software, we are referring to freedom, not 326 the Program is not required to print an announcement.) 374 special exception, the source code distributed need not include 394 5. You are not required to accept this License, since you have not 406 these terms and conditions. You may not impose any further [all …]
A D	BRANCHES.md	19 These branches will not receive any changes or updates. 35 code that's working and secure with Mbed TLS x.y.z and does not rely on 43 result in an incompatible API or ABI, although features will generally not 45 cryptographic algorithm does not break code that does not use that 50 not considered API compatibility breaks: 55 * Returning an error code that was not previously documented for a function 82 Note that this guarantee does not currently fully extend to drivers, which 86 as the use of driver state, we do not yet guarantee backward compatibility.
A D	BUGS.md	13 your issue has already been reported. If not, … 16 [`SECURITY.md`](SECURITY.md). If not, … 19 Please do not use GitHub for support questions. If you want to know
/mbedtls/docs/architecture/psa-migration/
A D	md-cipher-dispatch.md	76 …not ready for production since it is not completed.” We may want to change this, for example, to a… 99 * Software implementations of primitive cryptographic mechanisms. These are not expected to change. 189 #### Why PSA is not always possible 194 * There is a PSA driver which has not been initialized (this happens in `psa_crypto_init()`). 207 * must not call PSA (or must have a fallback) if their caller is not in the PSA domain and the PSA … 288 …t are available through accelerators but not through legacy, but this is not officially supported … 310 The existing interface in `md.h` is close to what we want, but not perfect. What's wrong with it? 332 This will go away naturally in 4.0 when this macros is not longer an option (because it's always on… 361 - CTR-DRBG can just check if `AES_C` is present and "fall back" to PSA if not. 529 This section is not necessary to implement MD light, but will cut down its code size. [all …]
A D	psa-legacy-bridges.md	37 There is functionality that is tied to one API and is not directly available in the other API: 41 * The legacy API has features that are not present (yet) in PSA, notably parsing and formatting asy… 75 * Where the PSA equivalents do not provide the same functionality. A typical example is parsing and… 92 Hashes do not involve keys, and involves no nontrivial data format. Therefore the only gap is with … 151 * A very common case where the input is a legacy key object is parsing. PSA does not (yet) have an … 274 * `mbedtls_pk_get_psa_attributes` does not change the id/lifetime fields of the attributes (which i… 292 * `mbedtls_pk_import_into_psa` does not need to check the bit-size in the attributes: `psa_import_k… 293 * `mbedtls_pk_import_into_psa` does not check that the policy in the attributes is sensible. That's… 306 * `pk` must be initialized, but not set up. 308 * It is an error if the key is not exportable. [all …]
A D	strategy.md	43 - it's not fully compatible with `MBEDTLS_ECP_RESTARTABLE`: you can enable 81 added to PSA in Mbed TLS 3.4, but support for ECDH is not present yet. 93 2. It's currently not possible to enable `MBEDTLS_PSA_CRYPTO_C` in 112 Taking advantage of the existing abstractions layers - or not 122 Note: key exchange (FFDH, ECDH) is not covered by an abstraction layer. 152 This strategy is not very well suited to the Cipher layer, as the PSA 160 part is not covered by PSA yet, if we decide to do that.) 183 be changed when setting up the context, but not when using it. In 283 - Step 1 is not achieved for all of the crypto library when it come to 305 for information management as well. However sometimes it may not be [all …]
/mbedtls/docs/proposed/
A D	psa-conditional-inclusion-c.md	6 This is currently a proposal for Mbed TLS. It is not currently on track for standardization in PSA. 30 [Req.inclusion] If the application does not require a mechanism, a suitably configured Mbed TLS bui… 32 …river is available in the build, a suitably configured Mbed TLS build must not include the corresp… 34 …es not require tools other than a C compiler. This is necessary to allow building an application a… 65 * If the symbol is not defined, the corresponding feature is not included. 79 …not requested for inclusion in the PSA Crypto configuration file, it may still be included in the … 106 …not specialized for any particular group, so reducing the number of available groups at compile ti… 129 These symbols are not part of the public interface of Mbed TLS towards applications or to drivers, … 141 …` is not set, the configuration of Mbed TLS works as before, and the inclusion of non-PSA code onl… 167 … `MBEDTLS_PSA_BUILTIN_xxx` symbols should not be visible to application code or driver code, since… [all …]
A D	psa-driver-interface.md	43 …mechanisms they support. A driver's code will not be invoked for cryptographic mechanisms that it … 109 * either the capability does not have an `"algorithms"` property; 115 * either the capability does not have a `"key_types"` property; 118 * either the capability does not have a `"key_sizes"` property; 548 * Other key types: not applicable. 666 Next parameters are return buffers (must not be null pointers). 670 * `PSA_ERROR_BAD_STATE`: the inputs are not ready 871 The init entry point does not take any parameter. 1080 * For a symmetric key (not a key pair or public key): 1263 * `PSA_ERROR_DOES_NOT_EXIST`: the requested key does not exist. [all …]
/mbedtls/ChangeLog.d/
A D	00README.md	3 This directory contains changelog entries that have not yet been merged 15 that are documented as experimental may or may not be announced, depending 30 changelog entry, but not for deciding whether to write one. 79 **Explain why, not how**. Remember that the audience is the users of the 80 library, not its developers. In particular, for a bug fix, explain the 81 consequences of the bug, not how the bug was fixed. For a new feature, explain
/mbedtls/docs/
A D	driver-only-builds.md	94 to low-level hash APIs (`mbedtls_sha256()` etc.) are not possible for the 183 - direct calls to APIs from the disabled modules are not possible; 184 - PK, X.509 and TLS will not support restartable ECC operations (see 210 curve is identified not by name, but by explicit parameters; 217 result in some code size savings, but not as much as when none of the 231 are not supported without `ECDH_C`. See also limitations regarding 256 interface does not support `KEY_PAIR_DERIVE`.) 391 (i.e. `PSA_WANT_xxx`) symbols is not always 1:1. For example: 430 - The legacy AES module (`MBEDTLS_AES_C`) is not enabled and 439 - The application is not using the `mbedtls_cipher_` API. [all …]
A D	3.0-migration-guide.md	25 migration path is not provided in prior documentation, changes made and the 34 suffixed with `_ret`. In Mbed TLS 3.x, this change may not be required, as most 92 This change does not affect users who use the default configuration; it only 111 not used in X.509, TLS or in PSA crypto, and it was not implemented in all 139 This only affects users who called the HAVEGE modules directly (not 202 not increase peak RAM usage anymore. 222 This does not affect users who use the default `mbedtls_config.h`. 521 This shouldn't affect users who took care not to include headers that 636 surface, even if the code is supposedly not used. 777 For users which do not rely on raw keys and IV, adjusting to the new [all …]

Completed in 124 milliseconds

1234567

Last Index update Fri Aug 22 08:59:00 CST 2025