| /openthread-latest/third_party/mbedtls/repo/tests/suites/ |
| D | test_suite_bignum_random.data | 70 MPI random in range: 1..2
73 MPI random in range: 1..3
76 MPI random in range: 1..4
79 MPI random in range: 1..5
82 MPI random in range: 1..6
85 MPI random in range: 1..7
88 MPI random in range: 1..8
91 MPI random in range: 1..9
94 MPI random in range: 1..10
97 MPI random in range: 1..11
[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_cipher.chacha20.data | 69 ChaCha20 Encrypt and decrypt 0 bytes in multiple parts 1
73 ChaCha20 Encrypt and decrypt 1 bytes in multiple parts 1
77 ChaCha20 Encrypt and decrypt 1 bytes in multiple parts 2
81 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 1
85 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 2
89 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 3
93 ChaCha20 Encrypt and decrypt 16 bytes in multiple parts 4
97 ChaCha20 Encrypt and decrypt 22 bytes in multiple parts 1
101 ChaCha20 Encrypt and decrypt 22 bytes in multiple parts 2
105 ChaCha20 Encrypt and decrypt 22 bytes in multiple parts 3
[all …]
|
| D | test_suite_cipher.aria.data | 65 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 0 bytes in multiple parts
69 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 1 bytes in multiple parts 1
73 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 1 bytes in multiple parts 2
77 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 16 bytes in multiple parts 1
81 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 16 bytes in multiple parts 2
85 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 16 bytes in multiple parts 3
89 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 16 bytes in multiple parts 4
93 ARIA-128 CCM*-NO-TAG - Encrypt and decrypt 22 bytes in multiple parts 1
97 ARIA-128-CCM*-NO-TAG - Encrypt and decrypt 22 bytes in multiple parts 2
101 ARIA-128-CCM*-NO-TAG - Encrypt and decrypt 23 bytes in multiple parts 1
[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.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 …]
|
| /openthread-latest/third_party/mbedtls/repo/library/ |
| D | ssl_debug_helpers_generated.c | 21 const char *mbedtls_ssl_named_group_to_str( uint16_t in ) in mbedtls_ssl_named_group_to_str() argument
23 switch( in ) in mbedtls_ssl_named_group_to_str()
65 const char *mbedtls_ssl_sig_alg_to_str( uint16_t in ) in mbedtls_ssl_sig_alg_to_str() argument
67 switch( in ) in mbedtls_ssl_sig_alg_to_str()
107 const char *mbedtls_ssl_states_str( mbedtls_ssl_states in ) in mbedtls_ssl_states_str() argument
109 switch (in) { in mbedtls_ssl_states_str()
176 const char *mbedtls_ssl_early_data_status_str( mbedtls_ssl_early_data_status in ) in mbedtls_ssl_early_data_status_str() argument
178 switch (in) { in mbedtls_ssl_early_data_status_str()
191 const char *mbedtls_ssl_protocol_version_str( mbedtls_ssl_protocol_version in ) in mbedtls_ssl_protocol_version_str() argument
193 switch (in) { in mbedtls_ssl_protocol_version_str()
[all …]
|
| D | ssl_debug_helpers.h | 22 const char *mbedtls_ssl_states_str(mbedtls_ssl_states in);
25 const char *mbedtls_ssl_early_data_status_str(mbedtls_ssl_early_data_status in);
26 const char *mbedtls_ssl_early_data_state_str(mbedtls_ssl_early_data_state in);
29 const char *mbedtls_ssl_protocol_version_str(mbedtls_ssl_protocol_version in);
31 const char *mbedtls_tls_prf_types_str(mbedtls_tls_prf_types in);
33 const char *mbedtls_ssl_key_export_type_str(mbedtls_ssl_key_export_type in);
35 const char *mbedtls_ssl_sig_alg_to_str(uint16_t in);
37 const char *mbedtls_ssl_named_group_to_str(uint16_t in);
|
| /openthread-latest/third_party/mbedtls/repo/ |
| D | ChangeLog | 6 * Remove `tls13_` in mbedtls_ssl_tls13_conf_early_data() and
8 feature may not be TLS 1.3 specific in the future. Fixes #6909.
11 * psa_import_key() now only accepts RSA keys in the PSA standard formats.
25 They are deprecated and will be removed in a future version of the
27 * mbedtls_ecp_write_key() is deprecated in favor of
44 * AES-NI is now supported in Windows builds with clang and clang-cl.
52 that use the decryption direction (ECB in PSA, CBC, XTS, KW) and with DES.
56 library without the corresponding built-in implementation. Generally
58 or they'll both be built in. However, for CCM and GCM the built-in
63 disabled. This requires PSA_WANT_ALG_ECB_NO_PADDING in addition to
[all …]
|
| D | .uncrustify.cfg | 43 # Braces on same line as keywords that follow them - 'else' and the 'while' in 'do {} while ()';
55 # Force exactly one space between ')' and '{' in statements
107 # No spaces inside the first parentheses in a function type
110 # (Uncrustify >= 0.74.0) No spaces inside parens in for statements
136 # But allow a space in the case of e.g. char * const x;
139 # Remove space after star in a function return type
142 # At least 1 space after a type in variable definition etc
150 # (Uncrustify >= 0.73.0) Remove space before a semi in a non-empty for
152 # (Uncrustify >= 0.73.0) Remove space in empty first statement of a for
154 # (Uncrustify >= 0.74.0) Remove space in empty middle statement of a for
[all …]
|
| D | README.md | 11 …in the fully documented configuration file `include/mbedtls/mbedtls_config.h`, which is also the p…
15 … configurations focused on specific use cases in the `configs/` directory. You can read more about…
24 To generate a local copy of the library documentation in HTML format, tailored to your compile-time…
41 …ays complete and up-to-date. The others should reflect all changes present in the CMake and Make b…
43 …epends on libmbedcrypto. As a result, some linkers will expect flags to be in a specific order, fo…
52 * Perl to run the tests, and to generate some source files in the development branch.
61 ### Generated source files in the development branch
63 …in the development branch of Mbed TLS, but the generated files are included in official releases. …
89 We intentionally only use a minimum of functionality in the makefiles in order to keep them as simp…
107 …he build environment is a Windows shell (for instance using mingw32-make) (in that case some targe…
[all …]
|
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/ |
| D | psa-storage-resilience.md | 5 …ct behavior of the key store even under if the underlying platform behaves in a non-nominal, but s…
15 …is concerned, at any given point in time, the system is either in a state where the function has n…
19 …n operation to an external system. For example, if a key creation function in the PSA Crypto API r…
34 …on). This also holds for an opaque key stored in a secure element that does not have its own key s…
40 …e-underlying-file-storage). We do not need to take any special precautions in the library design, …
46 …in a stateful secure element, i.e. a secure element that stores keys. This excludes keys in a stat…
50 **Assumption: driver calls for key management in stateful secure elements are atomic and committing…
63 …in storage that are related to the non-existent key. If the core loses power between steps 2 and 3…
67 Accomplishing a transaction across system boundaries is a well-known problem in database management…
71 …in a stateful secure element, a successful creation process goes as follows (see [“Key management …
[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 …in a psa_crypto_driver_wrappers.h header file, the non-static ones are generated in a psa_crypto_d…
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 …]
|
| D | mbed-crypto-storage-specification.md | 5 Key storage was originally introduced in a product called Mbed Crypto, which was re-distributed via…
18 Released in November 2018. <br>
19 Integrated in Mbed OS 5.11.
39 …nformation about each key is stored in a dedicated file whose name is constructed from the key ide…
41 …range from 1 to 0xfffeffff. This limitation on the range is not documented in user-facing document…
43 The code uses the following constant in an internal header (note that despite the name, this value …
51 All integers are encoded in little-endian order in 8-bit bytes.
83 …in a directory other than the current directory. This value is simply prepended to the file name (…
94 Released in February 2019. <br>
95 Integrated in Mbed OS 5.12.
[all …]
|
| D | tls13-support.md | 75 Note that in absence of an application profile standard specifying otherwise
83 - TLS 1.2 and TLS 1.3 can be enabled in the build independently of each
89 configuration options in the sense that when enabling TLS 1.3 in the library
132 (1) These options must remain in their default state of enabled.
138 compatibility mode as defined in section D.4 of RFC 8446.
166 work to reduce review rounds and the number of comments in each round. They
181 - Use TLS1_3 in TLS 1.3 specific macros.
183 - The names of macros and variables related to a field or structure in the
185 it is in the specification. If the field name is "too long" and we prefer
187 everywhere in the code.
[all …]
|
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/psa-migration/ |
| D | testing.md | 4 This document records the testing strategy used so far in implementing
11 There needs to be at least one build in `all.sh` that enables
16 ensured by the fact that it's disabled in the default config.
35 in order to create PK contexts that can then be passed to existing TLS and
41 - in `test_suite_pk` we have a new test function `pk_psa_utils` that exercises
45 - in `test_suite_pk` we modified the existing `pk_psa_sign` test function to
47 - in `test_suite_pkwrite` we should have a new test function checking that
52 - in `programs/ssl/ssl_client2` a new option `key_opaque` that causes the
53 new API to be used, and one or more tests in `ssl-opt.sh` using that.
55 - in `test_suite_x509write` we have a new test function
[all …]
|
| D | strategy.md | 1 This document explains the strategy that was used so far in starting the
21 As of early 2023, work towards G5 is in progress: Mbed TLS 3.3 and 3.4 saw
22 some improvements in this area, and more will be coming in future releases.
35 - `MBEDTLS_USE_PSA_CRYPTO` - disabled by default (enabled in "full" config),
36 controls usage of PSA Crypto APIs to perform operations in X.509 and TLS
45 documentation of this option in `mbedtls_config.h`);
67 backward compatibility issues, and in particular if the cost of implementing
74 Currently this option controls not only the presence of restartable APIs in
75 the crypto library, but also their use in the TLS and X.509 layers. Since PSA
81 added to PSA in Mbed TLS 3.4, but support for ECDH is not present yet.
[all …]
|
| D | psa-limitations.md | 2 1.1) that may impact our ability to (1) use it for all crypto operations in
3 TLS and X.509 and (2) support isolation of all long-term secrets in TLS (that
4 is, goals G1 and G2 in [strategy.md](strategy.md) in the same directory).
7 operations done in TLS and X.509 code, but of course it's still possible that
17 Support for interruptible ECDSA sign/verify was added to PSA in Mbed TLS 3.4.
25 both enabled, some operations that should be restartable are not (ECDH in TLS
28 they use the legacy API instead, in order to get restartable behaviour.
30 Things that are in the API but not implemented yet
33 PSA Crypto has an API for FFDH, but it's not implemented in Mbed TLS yet.
42 (See also the first paragraph in the previous section.)
[all …]
|
| D | md-cipher-dispatch.md | 12 A difference between the original strategy and the current one is that in this work, we are not tre…
22 so that my code keeps working in new minor versions of Mbed TLS.
28 so that my code works in all Mbed TLS configurations.
30 Note: this is the same problem we face in X.509 and TLS.
35 I want to build Mbed TLS in a way that uses my hardware wherever relevant,
46 to avoid bugs in “unusual” configurations.
56 …PSA interfaces to use PSA interfaces under the hood, without breaking code in the cases where this…
58 …kely has better performance, and sometimes better security, than the built-in software implementat…
60 …the duplication between the implementations of HMAC in `md.c` and in `psa_crypto_mac.c`, and HKDF …
88 …d, applications must call `psa_crypto_init()` before calling any of the functions in these modules.
[all …]
|
| /openthread-latest/third_party/mbedtls/repo/docs/ |
| D | driver-only-builds.md | 3 built-in implementation of those algorithms), from a user's perspective.
7 aggressively optimized for code size than the default one in Mbed TLS.
26 configuration of cryptographic algorithms using `PSA_WANT` macros in
28 mechanism through the PSA API in Mbed
33 - Define the corresponding `PSA_WANT` macro in `psa/crypto_config.h` - this
34 means the algorithm will be available in the PSA Crypto API.
35 - Define the corresponding `MBEDTLS_PSA_ACCEL` in your build. This could be
36 defined in `psa/crypto_config.h` or your compiler's command line. This
38 - Undefine / comment out the corresponding `MBEDTLS_xxx_C` macro in
39 `mbedtls/mbedtls_config.h`. This ensures the built-in implementation is not
[all …]
|
| D | use-psa-crypto.md | 19 **Why enable this option:** to fully take advantage of PSA drivers in PK,
21 for ECDSA, ECDH and EC J-PAKE in those modules. However, note that even with
22 this option disabled, some code in PK, X.509, TLS or the crypto library might
27 `MBEDTLS_PSA_CRYPTO_C`. These two options differ in the following way:
31 modules in the library (non-PSA crypto APIs, X.509, TLS) may or may not use
53 still beta and not ready for production, so we made its use in X.509 and TLS
54 opt-in: by default, these modules would keep using the stable,
58 its use in other modules opt-in. However, PSA Crypto functions require that
64 reasons, we can't extend its scope. However, new modules in the library, such
70 ### PSA-held (opaque) keys in the PK layer
[all …]
|
| /openthread-latest/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-latest/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-latest/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 of this kind, so we will only mention them in the Changelog if they are
28 Until Mbed TLS 2.24.0, we required changelog entries in more cases.
50 <!-- Keep this synchronized with STANDARD_CATEGORIES in assemble_changelog.py! -->
62 Use “Changes” for anything that doesn't fit in the other categories.
71 bug in mbedtls_xxx() ….”
82 why one might be interested in the feature. For an API change or a deprecation,
[all …]
|
| /openthread-latest/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 internal header files from `library/`. Do no…
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 …]
|
