| /mbedtls-3.6.0/library/ |
| D | psa_crypto_se.c | 48 psa_drv_se_internal_context_t internal; member
116 if (driver->u.internal.persistent_data_size > UINT32_MAX) { in psa_get_se_driver_its_file_uid()
145 (uint32_t) driver->u.internal.persistent_data_size, in psa_load_se_persistent_data()
146 driver->u.internal.persistent_data, in psa_load_se_persistent_data()
165 (uint32_t) driver->u.internal.persistent_data_size, in psa_save_se_persistent_data()
166 driver->u.internal.persistent_data, in psa_save_se_persistent_data()
211 driver->u.internal.persistent_data, in psa_find_se_slot_for_key()
227 driver->u.internal.persistent_data, in psa_find_se_slot_for_key()
253 driver->u.internal.persistent_data, in psa_destroy_se_key()
271 driver->u.internal.persistent_data, in psa_init_all_se_drivers()
[all …]
|
| /mbedtls-3.6.0/tests/scripts/ |
| D | list-identifiers.sh | 27 -i|--internal)
45 Sorry, this script has to be called with --internal.
48 iteration of list-identifiers.sh, of which only the --internal option remains in
|
| /mbedtls-3.6.0/docs/architecture/testing/ |
| D | invasive-testing.md | 32 ### Reliance on internal details
34 In unit tests and in test programs, it's ok to include internal header files from `library/`. Do no…
38 If test code or test data depends on internal details of the library and not just on its documented…
73 In unit test code that needs to modify the internal behavior:
89 …umented behavior of the product, to avoid extra work when the product's internal or implementation…
125 Sometimes it is useful to peek or poke internal data.
127 * Check consistency of internal data (e.g. output of key generation).
162 …internal interfaces, mostly intended for cross-module abstraction leakage rather than for testing.…
174 We can write tests that call internal functions that are not exposed in the public interfaces. This…
178 …internal interfaces need to be used correctly. We may accidentally rely on internal details in the…
[all …]
|
| /mbedtls-3.6.0/docs/architecture/ |
| D | psa-storage-resilience.md | 115 …sumptions-on-the-underlying-file-storage), each atomic operation in the internal storage concerns …
117 A key creation function must transform the internal storage from a state where file `id` does not e…
119 …is not possible with a stateful secure element because the state of the internal storage needs to …
121 …nging the state of the secure element, there must be information in the internal storage that indi…
129 …a different state after that, this will require a total of 4 updates to internal storage. Since we…
289 * Normal operation must maintain a certain invariant on the state of the world (internal storage an…
303 …e key must be present in the secure element if and only if the key file is in the internal storage.
325 …cure element, and if it does, keep it and keep `id`. If not, remove `id` from the internal storage.
334 If `id` is in the transaction list, neither the state of `id` in the internal storage nor the state…
341 …cure element, and if it does, keep it and keep `id`. If not, remove `id` from the internal storage.
[all …]
|
| D | mbed-crypto-storage-specification.md | 43 The code uses the following constant in an internal header (note that despite the name, this value …
137 * Files 0 through 0xffffff51, 0xffffff53 through 0xffffffff: unused, reserved for internal use of t…
166 …-bit owner, with a nonzero value, and thus reserve the range 0–0xffffffff for internal library use.
235 * Files 0xffff0000 through 0xffffffff: reserved for internal use of the crypto library or crypto se…
246 * Files 0xffff0000 through 0xffffffff: reserved for internal use of the crypto library or crypto se…
251 File identifiers in the range 0xffff0000 through 0xffffffff are reserved for internal use in Mbed C…
292 * key identifier (4 bytes in a library integration, 8 bytes on a PSA platform): the internal repres…
374 * Files 0xffff0000 through 0xffffffff: reserved for internal use of the crypto library or crypto se…
385 * Files 0xffff0000 through 0xffffffff: reserved for internal use of the crypto library or crypto se…
431 File identifiers that are outside the range of persistent key identifiers are reserved for internal…
[all …]
|
| D | psa-crypto-implementation-structure.md | 60 Key creation implementation in Mbed TLS PSA core is articulated around three internal functions: ps…
|
| D | tls13-support.md | 211 internal to C modules.
|
| /mbedtls-3.6.0/tests/suites/ |
| D | test_suite_psa_crypto_se_driver_hal.data | 151 Key registration: invalid lifetime (volatile internal storage)
154 Key registration: invalid lifetime (internal storage)
|
| D | test_suite_entropy.function | 49 * are internal changes to how entropy sources are registered.
499 // Determine what should have happened with manual entropy internal logic
|
| D | test_suite_pkparse.function | 96 * not because this is already done by the internal "pk_get_ecpubkey()"
|
| D | test_suite_psa_crypto_persistent_key.function | 4 * access internal key storage functions directly. Some of the tests depend
|
| D | test_suite_psa_crypto_storage_format.function | 208 * hash internally only dispatch to the internal md module, not to
|
| D | test_suite_x509write.function | 55 /* Note: this can't happen except after an internal error */
|
| D | test_suite_cipher.function | 13 /* Check the internal consistency of a cipher info structure, and
|
| D | test_suite_ecp.function | 847 // Convert exp_A to internal representation (A+2)/4
|
| /mbedtls-3.6.0/3rdparty/p256-m/p256-m/ |
| D | README.md | 50 public API), one for open-box testing (for unit-testing internal functions,
62 - The code is small and well documented, including internal APIs: with the
331 internal `u32_muladd64()` function, as well as two pure C versions of this
401 wrappers around internal functions, just taking care of format conversions and
429 There are 4 versions of the internal function `u32_muladd64`: two assembly
537 defined type throughout the internal APIs, and then on 64-bit platforms define
|
| /mbedtls-3.6.0/docs/architecture/psa-migration/ |
| D | testing.md | 64 New APIs meant for internal use
|
| D | md-cipher-dispatch.md | 12 …ating PSA as a black box. We can change experimental features, and we can call internal interfaces.
101 …nterface. This is not expected to change, except perhaps to expose some internal functionality to …
139 …s `psa_crypto_init()`). A possible workaround may be to dispatch to the internal functions that ar…
325 #### MD light internal support macros
|
| D | strategy.md | 19 internal changes implement (G1).
265 configuration", to allow working around internal crypto dependencies when
296 - for ECC, we have no internal uses of the top-level algorithms (ECDSA, ECDH,
|
| /mbedtls-3.6.0/docs/ |
| D | use-psa-crypto.md | 138 All of these internal changes are active as soon as `MBEDTLS_USE_PSA_CRYPTO`
|
| D | 3.0-migration-guide.md | 494 configuration options) may have their own internal and are free to ignore the
522 were documented as internal, despite being in the public include directory.
|
| /mbedtls-3.6.0/ |
| D | README.md | 281 * The API distinguishes caller memory from internal memory, which allows the library to be implemen…
282 * The structure of internal data is hidden to the application, which allows substituting alternativ…
|
| D | ChangeLog | 378 backed by internal library support for ECDSA signing and verification.
1064 * Add the internal implementation of and support for CCM to the PSA multipart
1091 and mbedtls_ssl_free() would cause an internal session buffer to
1217 * Move internal headers.
1218 Header files that were only meant for the library's internal use and
1595 effect on Mbed TLS's internal use of mbedtls_mpi_gcd(), but may affect
1672 as always 0. It is now reserved for internal purposes and may take
1724 * Fix an errorneous estimation for an internal buffer in
1842 obtain entropy, or due to an internal failure (which, for Mbed TLS's own
2343 structures, which was exposed only in an internal header.
[all …]
|
| /mbedtls-3.6.0/docs/proposed/ |
| D | psa-driver-interface.md | 781 * The size of the key data buffer `key_buffer` is sufficient for the internal representation of the…
964 …supply entropy to the driver. The driver must mix this entropy into its internal state. The driver…
1050 …esent application keys as wrapped key material, but built-in keys by an internal identifier that t…
1129 * `"allocate_key"`: this function obtains an internal identifier for the key. This may be, for exam…
1130 * `"destroy_key"`: this function invalidates the internal identifier and destroys the associated ke…
1144 …er's `"allocate_key"` entry point. This function typically allocates an internal identifier for th…
1159 …nd is not accessible to drivers. Some typical strategies to allocate an internal key identifier ar…
|
| D | psa-conditional-inclusion-c.md | 165 #### Visibility of internal symbols
|
