Searched refs:very (Results 1 – 25 of 26) sorted by relevance
12
| /openthread-latest/third_party/mbedtls/repo/tests/data_files/dir-maxpath/ |
| D | Readme.txt | 1 These certificates form a very long chain, used to test the
|
| /openthread-latest/third_party/jlink/ |
| D | README.md | 18 well as sending input to the application at a very high speed without affecting
|
| /openthread-latest/third_party/mbedtls/repo/tests/suites/ |
| D | test_suite_timing.function | 5 * this suite only performs very basic sanity checks of the timing API.
|
| D | test_suite_platform.function | 5 * this suite only performs very basic sanity checks of the timing API.
|
| D | test_suite_bignum_random.function | 33 * range where any output out of range would be very likely to lead to a
337 * enough. This is a very crude way of checking the distribution.
|
| D | test_suite_psa_its.function | 53 * remove() on an existing file is very unlikely anyway and would not
|
| D | test_suite_bignum.misc.data | 739 Regression mbedtls_mpi_add_abs (add small to very large MPI with carry rollover) [#1]
742 Regression mbedtls_mpi_add_abs (add small to very large MPI with carry rollover) [#2]
|
| D | test_suite_psa_crypto_slot_management.function | 749 * to PSA_KEY_ID_VOLATILE_MAX included. It is very unlikely that
|
| D | test_suite_ssl.function | 4913 * The contents of the early data are not very important, write a
4965 * max_early_data_size limit but if max_early_data_size is very
|
| D | test_suite_ecp.data | 1030 ECP mod p521 very small
|
| D | test_suite_ssl.data | 3343 TLS 1.3 cli, maximum early data size, very small but not 0
|
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/testing/ |
| D | invasive-testing.md | 60 …fine extra functions. It may add fields to structures, but if so, make it very clear that these fi…
139 * !! requirement is very problematic
147 Mbed TLS traditionally has very fine-grained public interfaces, with many platform functions that c…
209 …not in production, we can add a compile-time option to enable it. This is very powerful and usuall…
250 This is a very powerful approach, but it comes with limitations:
255 * Debugger scripts are very much non-portable.
|
| /openthread-latest/third_party/mbedtls/repo/ |
| D | BRANCHES.md | 90 For the LTS branches, additionally we try very hard to also maintain ABI
|
| D | CONTRIBUTING.md | 48 …, the fix should be reworked to avoid the API change. API changes without very strong justificatio…
|
| D | ChangeLog | 501 * Fix very high stack usage in SSL debug code. Reported by Maximilian
530 with a very minimal configuration. Fixes #7625.
1759 An adversary who is capable of very precise timing measurements could
3963 * Add checks to prevent signature forgeries for very large messages while
4039 with RFC-5116 and could lead to session key recovery in very long TLS
4473 * Removed openssl.h (very partial OpenSSL compatibility layer).
|
| /openthread-latest/third_party/mbedtls/repo/docs/proposed/ |
| D | psa-conditional-inclusion-c.md | 100 …_WANT_ECC_FAMILY_xxx`. This deviation is justified by the fact that it is very common to wish to i…
225 The two mechanisms have very different designs. Is there serious potential for confusion? Do we und…
|
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/psa-migration/ |
| D | md-cipher-dispatch.md | 293 …SA when `MBEDTLS_PSA_CRYPTO_C` is enabled. This would only save at best a very small amount of cod…
318 …fo_t` can become a very thin type. We can't remove the extra function call from the source code of…
356 The two AEAD modes, GCM and CCM, have very similar needs and positions in the stack, strongly sugge…
|
| D | psa-legacy-bridges.md | 86 …allback (returning `MBEDTLS_ERR_xxx`) on top of PSA functions, but this is a very limited use case.
151 * A very common case where the input is a legacy key object is parsing. PSA does not (yet) have an …
|
| D | strategy.md | 152 This strategy is not very well suited to the Cipher layer, as the PSA
|
| /openthread-latest/third_party/mbedtls/repo/3rdparty/p256-m/p256-m/ |
| D | README.md | 491 shapes (Montgomery, (twisted) Edwards), this layer would probably look very
512 very different implementation.
|
| /openthread-latest/third_party/mbedtls/repo/docs/ |
| D | 3.0-migration-guide.md | 672 These days clients are very unlikely to do that. If you have a client that
996 issuing only the very last call to `mbedtls_ssl_set_session()`.
1020 ….ietf.org/doc/html/rfc8422#section-5.1.1) deprecates it in TLS, and it is very rarely used, althou…
|
| D | driver-only-builds.md | 252 There is very limited support for having acceleration for only a subset of the
|
| D | psa-transition.md | 34 * Mbed TLS APIs are traditionally very transparent: the caller can access internal fields of operat…
784 …single format that just contains the number(s) that make up the key, with very little metadata. Th…
|
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/ |
| D | psa-shared-memory.md | 96 Note that although copying is very easy to write into a program, there is a risk that a compiler (e…
109 These rules are very difficult to enforce.
340 …r performance or accuracy as required. This should be simple as both have very similar memory pois…
|
| /openthread-latest/doc/ |
| D | Doxyfile.in | 607 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
|
12
