/openthread-3.6.0/third_party/mbedtls/repo/tests/suites/ |
D | test_suite_aes.function | 211 * otherwise we wouldn't get to the size check we're interested in. */ 372 const unsigned char in[16] = { 0 }; 408 valid_mode, in, out ) ); 411 invalid_mode, in, out ) ); 417 valid_mode, in, NULL ) ); 423 out, in, out ) ); 427 out, in, out ) ); 431 NULL, in, out ) ); 439 out, in, NULL ) ); 446 in, in, out ) ); [all …]
|
D | test_suite_cipher.chacha20.data | 65 ChaCha20 Encrypt and decrypt 0 bytes in multiple parts 1 69 ChaCha20 Encrypt and decrypt 1 bytes in multiple parts 1 73 ChaCha20 Encrypt and decrypt 1 bytes in multiple parts 2 77 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 1 81 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 2 85 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 3 89 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 4 93 ChaCha20 Encrypt and decrypt 22 bytes in multiple parts 1 97 ChaCha20 Encrypt and decrypt 22 bytes in multiple parts 2 101 ChaCha20 Encrypt and decrypt 22 bytes in multiple parts 3 [all …]
|
D | test_suite_cipher.arc4.data | 65 ARC4 Encrypt and decrypt 0 bytes in multiple parts 69 ARC4 Encrypt and decrypt 1 bytes in multiple parts 1 73 ARC4 Encrypt and decrypt 1 bytes in multiple parts 2 77 ARC4 Encrypt and decrypt 16 bytes in multiple parts 1 81 ARC4 Encrypt and decrypt 16 bytes in multiple parts 2 85 ARC4 Encrypt and decrypt 16 bytes in multiple parts 3 89 ARC4 Encrypt and decrypt 16 bytes in multiple parts 4 93 ARC4 Encrypt and decrypt 22 bytes in multiple parts 1 [#1] 97 ARC4 Encrypt and decrypt 22 bytes in multiple parts 1 [#2] 101 ARC4 Encrypt and decrypt 22 bytes in multiple parts 1 [#3] [all …]
|
D | test_suite_cipher.null.data | 57 NULL Encrypt and decrypt 1 bytes in multiple parts 1 61 NULL Encrypt and decrypt 1 bytes in multiple parts 2 65 NULL Encrypt and decrypt 16 bytes in multiple parts 1 69 NULL Encrypt and decrypt 16 bytes in multiple parts 2 73 NULL Encrypt and decrypt 16 bytes in multiple parts 3 77 NULL Encrypt and decrypt 16 bytes in multiple parts 4 81 NULL Encrypt and decrypt 22 bytes in multiple parts 1 [#1] 85 NULL Encrypt and decrypt 22 bytes in multiple parts 1 [#2] 89 NULL Encrypt and decrypt 22 bytes in multiple parts 1 [#3] 93 NULL Encrypt and decrypt 32 bytes in multiple parts 1
|
D | test_suite_mpi.data | 322 Base test mbedtls_mpi_lt_mpi_ct (X is longer in storage) 325 Base test mbedtls_mpi_lt_mpi_ct (Y is longer in storage) 676 Shrink 0 limbs in a buffer of size 0 to 0 679 Shrink 2 limbs in a buffer of size 2 to 4 682 Shrink 2 limbs in a buffer of size 4 to 4 685 Shrink 2 limbs in a buffer of size 8 to 4 688 Shrink 4 limbs in a buffer of size 8 to 4 691 Shrink 6 limbs in a buffer of size 8 to 4 yielding 6 694 Shrink 2 limbs in a buffer of size 4 to 0 yielding 2 697 Shrink 1 limbs in a buffer of size 4 to 0 yielding 1 [all …]
|
D | test_suite_cipher.chachapoly.data | 65 ChaCha20+Poly1305 Encrypt and decrypt 0 bytes in multiple parts 1 69 ChaCha20+Poly1305 Encrypt and decrypt 1 bytes in multiple parts 1 73 ChaCha20+Poly1305 Encrypt and decrypt 1 bytes in multiple parts 2 77 ChaCha20+Poly1305 Encrypt and decrypt 16 bytes in multiple parts 1 81 ChaCha20+Poly1305 Encrypt and decrypt 16 bytes in multiple parts 2 85 ChaCha20+Poly1305 Encrypt and decrypt 16 bytes in multiple parts 3 89 ChaCha20+Poly1305 Encrypt and decrypt 16 bytes in multiple parts 4 93 ChaCha20+Poly1305 Encrypt and decrypt 22 bytes in multiple parts 1 97 ChaCha20+Poly1305 Encrypt and decrypt 22 bytes in multiple parts 2 101 ChaCha20+Poly1305 Encrypt and decrypt 22 bytes in multiple parts 3 [all …]
|
D | test_suite_cipher.camellia.data | 309 CAMELLIA Encrypt and decrypt 0 bytes in multiple parts [#1] 313 CAMELLIA Encrypt and decrypt 1 bytes in multiple parts 1 [#1] 317 CAMELLIA Encrypt and decrypt 1 bytes in multiple parts 2 [#1] 321 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 1 [#1] 325 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 2 [#1] 329 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 3 [#1] 333 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 4 [#1] 337 CAMELLIA Encrypt and decrypt 22 bytes in multiple parts 1 [#1] 341 CAMELLIA Encrypt and decrypt 22 bytes in multiple parts 1 [#2] 345 CAMELLIA Encrypt and decrypt 22 bytes in multiple parts 1 [#3] [all …]
|
D | test_suite_cipher.blowfish.data | 305 BLOWFISH Encrypt and decrypt 0 bytes in multiple parts [#1] 309 BLOWFISH Encrypt and decrypt 1 bytes in multiple parts 1 [#1] 313 BLOWFISH Encrypt and decrypt 1 bytes in multiple parts 2 [#1] 317 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 1 [#1] 321 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 2 [#1] 325 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 3 [#1] 329 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 4 [#1] 333 BLOWFISH Encrypt and decrypt 22 bytes in multiple parts 1 [#1] 337 BLOWFISH Encrypt and decrypt 22 bytes in multiple parts 1 [#2] 341 BLOWFISH Encrypt and decrypt 22 bytes in multiple parts 1 [#3] [all …]
|
D | test_suite_cipher.des.data | 313 DES Encrypt and decrypt 0 bytes in multiple parts 317 DES Encrypt and decrypt 1 bytes in multiple parts 1 321 DES Encrypt and decrypt 1 bytes in multiple parts 2 325 DES Encrypt and decrypt 16 bytes in multiple parts 1 329 DES Encrypt and decrypt 16 bytes in multiple parts 2 333 DES Encrypt and decrypt 16 bytes in multiple parts 3 337 DES Encrypt and decrypt 16 bytes in multiple parts 4 341 DES Encrypt and decrypt 22 bytes in multiple parts 1 [#1] 345 DES Encrypt and decrypt 22 bytes in multiple parts 1 [#2] 349 DES Encrypt and decrypt 22 bytes in multiple parts 1 [#3] [all …]
|
D | test_suite_memory_buffer_alloc.data | 4 Memory buffer alloc - free in middle, alloc at end 7 Memory buffer alloc - free in middle, realloc 10 Memory buffer alloc - free in middle, merge, realloc
|
/openthread-3.6.0/third_party/mbedtls/repo/ |
D | ChangeLog | 6 * Some fields of mbedtls_ssl_session and mbedtls_ssl_config are in a 16 which allowed SHA-1 in the default TLS configuration for certificate 17 signing. It was intended to facilitate the transition in environments 32 is currently implemented in the AES, DES and md modules, and will be 33 extended to other modules in the future. 41 value when verifying a MAC or AEAD tag. This hardens the library in 44 man-in-the-middle to inject fake ciphertext into a DTLS connection. 47 oracle vulnerability if the output buffer is in memory that is shared with 57 * The GNU makefiles invoke python3 in preference to python except on Windows. 62 * Fix a parameter set but unused in psa_crypto_cipher.c. Fixes #4935. [all …]
|
D | BRANCHES.md | 3 At any point in time, we have a number of maintained branches consisting of: 15 API compatibility in the `master` branch between major version changes. We 21 We maintain API compatibility in released versions of Mbed TLS. If you have 28 insecure in the meantime (for example, crypto that was found to be weak) may 29 need to be changed. In case security comes in conflict with backwards 35 re-compiling) and to avoid any increase in code size or RAM usage, or in the 37 before, is in case those goals would conflict with fixing a security issue, we 39 had to break ABI compatibility in an LTS branch, but we occasionally had to
|
D | dco.txt | 17 (a) The contribution was created in whole or in part by me and I 19 indicated in the file; or 24 work with modifications, whether created in whole or in part 27 in the file; or
|
/openthread-3.6.0/tests/scripts/thread-cert/ |
D | requirements.txt | 5 # pip-compile requirements.in 8 # via -r requirements.in 14 # via -r requirements.in 20 # via -r requirements.in 22 # via -r requirements.in
|
/openthread-3.6.0/third_party/mbedtls/repo/docs/architecture/ |
D | mbed-crypto-storage-specification.md | 16 Released in November 2018. <br> 17 Integrated in Mbed OS 5.11. 37 …nformation about each key is stored in a dedicated file whose name is constructed from the key ide… 39 …range from 1 to 0xfffeffff. This limitation on the range is not documented in user-facing document… 41 The code uses the following constant in an internal header (note that despite the name, this value … 49 All integers are encoded in little-endian order in 8-bit bytes. 81 …in a directory other than the current directory. This value is simply prepended to the file name (… 92 Released in February 2019. <br> 93 Integrated in Mbed OS 5.12. 110 …in a dedicated file designated by the key identifier. In integrations where there is no concept of… [all …]
|
D | psa-crypto-implementation-structure.md | 11 …yptography API implementation is made of a core and PSA drivers as defined in the PSA driver inter… 16 * The organization of the software cryptographic implementations in drivers promotes modularization… 17 …ctionalities can be described by a JSON driver description file as defined in the PSA driver inter… 22 The core implements all the APIs as defined in the PSA Cryptography API specification but does not … 47 * clean-up in case of error ... */ 52 …. The implementations are generated in a psa_crypto_driver_wrappers.c C file and the function prot… 56 …in this generated file are guarded by pre-processor directives based on PSA_WANT_xyz macros (see [… 60 Key creation implementation in Mbed TLS PSA core is articulated around three internal functions: ps… 62 …t allocates a key slot, prepares it with the specified key attributes, and in case of a volatile k… 71 …in the following) is a driver in the sense that it is compliant with the PSA driver interface spec… [all …]
|
/openthread-3.6.0/tests/toranj/ |
D | README.md | 8 - `toranj-ncp` which enables testing of the combined behavior of OpenThread (in NCP mode), spinel i… 12 - It is developed in Python. 15 - `toranj` in NCP mode runs `wpantund` natively with OpenThread in NCP mode on simulation platform … 16 - `toranj` in CLI mode runs `ot-cli-ftd` on simulation platform (real-time). 17 - `toranj` tests run as part of GitHub Actions pull request validation in OpenThread and `wpantund`… 26 …arpet#/media/File:Toranj_-_special_circular_design_of_Iranian_carpets.JPG) used in Persian carpets.
|
/openthread-3.6.0/third_party/mbedtls/repo/docs/proposed/ |
D | psa-driver-integration-guide.md | 4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.** 8 …lemented in Mbed TLS yet and is disabled by default. You can enable the experimental work in progr… 16 …* in JSON format and some code to include in the build. The driver code can either be provided in … 22 1. Activate `MBEDTLS_PSA_CRYPTO_DRIVERS` in the library configuration.
|
D | psa-driver-developer-guide.md | 4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.** 10 …lemented in Mbed TLS yet and is disabled by default. You can enable the experimental work in progr… 20 * **Transparent** drivers implement cryptographic operations on keys that are provided in cleartext… 25 …in a **driver description file**. The driver description file declares which functions the driver … 27 …ver description file is JSON. The structure of this JSON file is specified in the section [“Driver… 31 * A driver description file (in JSON format). 32 …red by the driver description. The names of these header files is declared in the driver descripti… 37 …pecified in the PSA Cryptography Driver Interface specification](psa-driver-interface.html#driver-…
|
D | psa-driver-interface.md | 4 This document describes an interface for cryptoprocessor drivers in the PSA cryptography API. This … 6 …ecification is work in progress and should be considered to be in a beta stage. There is ongoing w… 12 …ns in a uniform way regardless of how the operations are performed. Under the hood, different keys… 14 …icies, and dispatches cryptographic operations either to the applicable driver or to built-in code. 16 Functions in the PSA Cryptography API invoke functions in the core. Code from the core calls driver… 22 * **Transparent** drivers implement cryptographic operations on keys that are provided in cleartext… 33 …hardware: accelerators that operate on keys in cleartext; cryptoprocessors that can wrap keys with… 35 …actions with platform-specific hardware happen only inside the driver (and in fact a driver need n… 47 …to implement some functions with C linkage, and to declare these functions in a **driver descripti… 49 …ver description file is JSON. The structure of this JSON file is specified in the section [“Driver… [all …]
|
/openthread-3.6.0/third_party/mbedtls/repo/docs/ |
D | use-psa-crypto.md | 20 defined is considered experimental and may change in incompatible ways at any 27 Some of these APIs are meant for the application to use in place of 28 pre-existing APIs, in order to get access to the benefits; in the sub-sections 29 below these are indicated by "Use in (X.509 and) TLS: opt-in", meaning that 34 layers; they are indicated below by "Use in (X.509 and) TLS: automatic", 38 ### PSA-held (opaque) keys in the PK layer 53 Use in X.509 and TLS: opt-in. The application needs to construct the PK context 54 using the new API in order to get the benefits; it can then pass the 81 exchanges will result in a handshake failure with the handshake function 84 Use in TLS: opt-in. The application needs to register the key using the new [all …]
|
/openthread-3.6.0/third_party/mbedtls/repo/ChangeLog.d/ |
D | 00README.md | 10 * Bug fixes in the library or in sample programs: fixing a security hole, 11 fixing broken behavior, fixing the build in some configuration or on some 13 * New features in the library, new sample programs, or new platform support. 14 * Changes in existing behavior. These should be rare. Changes in features 25 Until Mbed TLS 2.24.0, we required changelog entries in more cases. 47 <!-- Keep this synchronized with STANDARD_CATEGORIES in assemble_changelog.py! --> 59 Use “Changes” for anything that doesn't fit in the other categories. 68 bug in mbedtls_xxx() ….” 79 why one might be interested in the feature. For an API change or a deprecation, 88 to move the entries from files in `ChangeLog.d` to the main `ChangeLog` file.
|
/openthread-3.6.0/third_party/mbedtls/repo/docs/architecture/testing/ |
D | invasive-testing.md | 5 … testing as much as possible: test the documented behavior of the product, in a realistic environm… 30 …ctical way of doing it another way. All public interfaces should be useful in at least some config… 34 In unit tests and in test programs, it's ok to include header files from `library/`. Do not define … 36 … part of the public API. Declare such functions in `library/*.h` and include the corresponding hea… 38 …ails of the library and not just on its documented behavior, add a comment in the code that explai… 41 > /* This test file is specific to the ITS implementation in PSA Crypto 59 * **Do not use `MBEDTLS_TEST_HOOKS` for security checks or assertions.** Security checks belong in … 69 …hat does nothing (not a macro, to avoid accidentally skipping side effects in its parameters), to … 71 …, or to a function that does nothing. The global variable is defined in a header in the `library` … 89 …tever the tests check is guaranteed behavior of the product which cannot change in future versions. [all …]
|
/openthread-3.6.0/third_party/mbedtls/repo/3rdparty/everest/ |
D | README.md | 1 The files in this directory stem from [Project Everest](https://project-everest.github.io/) and are… 3 …in the [F* language](https://github.com/fstarlang/fstar) by [KreMLin](https://github.com/fstarlang… 5 …in `everest/library/legacy` should work on most systems. The main issue is that some platforms do …
|
/openthread-3.6.0/third_party/mbedtls/repo/doxygen/ |
D | mbedtls.doxyfile | 7 # in front of the TAG it is preceding . 19 # This tag specifies the encoding used for all characters in the config file 46 # included in the documentation. The maximum height of the logo should not 60 # 4096 sub-directories (in 2 levels) under the output directory of each output 63 # source files, where putting all generated files in the same directory would 68 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 70 # information to generate all constant output in the proper language. 82 # include brief member descriptions after the members that are listed in 96 # that is used to form the text in various listings. Each string 97 # in this list, if found as the leading text of the brief description, will be [all …]
|