| /mbedtls-development/library/ |
| A D | hkdf.c | 84 size_t where = 0; in mbedtls_hkdf_expand() local
176 num_to_copy = i != n ? hash_len : okm_len - where; in mbedtls_hkdf_expand()
177 memcpy( okm + where, t, num_to_copy ); in mbedtls_hkdf_expand()
178 where += hash_len; in mbedtls_hkdf_expand()
|
| /mbedtls-development/ChangeLog.d/ |
| A D | check-return.txt | 6 where this function cannot fail, or full-module replacements with
13 (where supported) for critical functions where ignoring the return
|
| A D | 00README.md | 67 the present tense. Use the imperative where applicable. For example: “Fix a
70 Include GitHub issue numbers where relevant. Use the format “#1234” for an
71 Mbed TLS issue. Add other external references such as CVE numbers where
74 Credit bug reporters where applicable.
|
| /mbedtls-development/ |
| A D | BRANCHES.md | 9 this is where the current major version of Mbed TLS (version 3.x) is being
41 * Changing which error code is returned in a case where multiple error
47 There are rare exceptions where we break API compatibility: code that was
|
| A D | .travis.yml | 38 # Add the directory where the Choco packages go
|
| A D | CONTRIBUTING.md | 22 …the [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) standard license header where possible.
30 …ruption to users, where a change to the interface is required, all changes to the ABI or API, even…
|
| A D | ChangeLog | 341 * Fix some cases in the bignum module where the library constructed an
355 where these are already defined, this can result in a compilation
365 * Fix test suite code on platforms where int32_t is not int, such as
445 now writing an empty string where it previously wrote one or more
528 |A| - |B| where |B| is larger than |A| and has more limbs (so the
557 enabled on platforms where freeing a mutex twice is not safe.
559 when MBEDTLS_THREADING_C is enabled on platforms where initializing
672 * Fix build failure in configurations where MBEDTLS_USE_PSA_CRYPTO is
1253 stdarg.h where needed. Fixes #2656.
1303 stdarg.h where needed. Fixes #2656.
[all …]
|
| A D | README.md | 11 …guration file `include/mbedtls/mbedtls_config.h`, which is also the place where features can be se…
282 There are currently a few deviations where the library does not yet implement the latest version of…
|
| A D | LICENSE | 79 where such license applies only to those patent claims licensable
|
| /mbedtls-development/tests/suites/ |
| A D | test_suite_net.function | 79 * platforms with a Unix-like select() function, which is where
122 * is problematic on the particular platform where the code is running,
|
| A D | test_suite_psa_crypto_persistent_key.data | 31 # Not specific to files, but only run this test in an environment where the maximum size could be r…
|
| A D | test_suite_ctr_drbg.function | 46 * where nonce||perso = nonce[nonce->len] */
|
| A D | test_suite_asn1parse.function | 298 * time, we skip some "boring" prefixes: we don't test prefixes where
443 * actual_mpi = 2^n where n is the length of the content
|
| A D | test_suite_mps.function | 250 * in the situation where a read request goes beyond the bounds of the
296 * in the situation where upon calling mbedtls_mps_reader_reclaim(), the
984 * where the request fails.
|
| A D | test_suite_pk.function | 218 /* In informational functions, we accept NULL where a context pointer
|
| /mbedtls-development/docs/architecture/ |
| A D | alternative-implementations.md | 28 On platforms where a hardware cryptographic engine is present, you can implement a driver for this …
37 * Enable `MBEDTLS_XXX_ALT` in the compile-time configuration where XXX is the module name. For exam…
45 …ld normally be `struct` types). This section lists some known limitations where the context type n…
52 …ble, and `mbedtls_ecp_point_read_binary()` must support a group structure where only `P`, `pbits`,…
|
| A D | mbed-crypto-storage-specification.md | 110 …where there is no concept of key owner (in particular, in library integrations), the key identifie…
115 * PSA service integration: the key file name is `(uint32_t)owner_uid << 32 | key_id` where `key_id`…
240 All integers are encoded in little-endian order in 8-bit bytes except where otherwise indicated.
299 All integers are encoded in little-endian order in 8-bit bytes except where otherwise indicated.
|
| A D | tls13-experimental.md | 266 length in bytes of the vector, where <vector name> is the name of the
301 likely not to be used in prototype where we now would use them in
|
| /mbedtls-development/docs/architecture/testing/ |
| A D | psa-storage-format-testing.md | 23 … the storage format by creating test cases under a version V of Mbed TLS, where the test case para…
31 Use a similar approach for files other than keys where possible and relevant.
66 Objective: test the format of the key file: which field goes where and how big it is.
|
| A D | driver-interface-test-strategy.md | 129 …river B, with one run where A returns `PSA_SUCCESS`, one where A returns `PSA_ERROR_NOT_SUPPORTED`…
|
| A D | invasive-testing.md | 7 The goal of this document is to identify areas where black-box testing is insufficient and to propo…
|
| /mbedtls-development/doxygen/ |
| A D | mbedtls.doxyfile | 53 # base path where the generated documentation will be put.
55 # where doxygen was started. If left blank the current directory will be used.
63 # source files, where putting all generated files in the same directory would
142 # relative paths, which will be relative from the directory where doxygen is
396 # 'anonymous_namespace{file}', where file will be replaced with the base
1287 # of to a relative location where the documentation can be found.
1408 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1449 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
1478 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
1654 # where "loc1" and "loc2" can be relative or absolute paths
[all …]
|
| /mbedtls-development/docs/ |
| A D | use-psa-crypto.md | 104 gracious fallback to the legacy API otherwise) in all places where a cipher is
125 Use in TLS and X.509: in all places where an ECDSA signature is verified.
|
| /mbedtls-development/docs/proposed/ |
| A D | psa-driver-interface.md | 306 …city, therefore this function does not need to do anything for algorithms where the output stream …
432 …where the PSA Cryptography implementation is a subsystem of a single application, the initializati…
488 This operation family requires the following type, entry points and parameters (TODO: where exactly…
548 …s on all the entropy sources that are available on the platform. A driver where a call to `"add_en…
590 If a transparent driver entry point is part of a capability where the `"fallback"` property is fals…
615 …stants. A typical value for `"base_size"` is `sizeof(acme_key_context_t)` where `acme_key_context_…
623 where `size_function` is the function named in the `"size_function"` property, `key_type` is the ke…
636 …where `public_key_overhead = PSA_EXPORT_PUBLIC_KEY_MAX_SIZE(key_type, key_bits)` if the `"store_pu…
647 where `key_bytes = ((key_bits + 7) / 8)` is the key size in bytes.
862 … 8–31 are a _location indicator_. This value indicates where the key material is stored and where …
[all …]
|
| A D | psa-conditional-inclusion-c.md | 52 …a/crypto_config.h` defines a series of symbols of the form `PSA_WANT_xxx` where `xxx` describes th…
142 The following table summarizes where symbols are defined depending on the configuration mode.
|