| /openthread-3.6.0/third_party/mbedtls/repo/doxygen/ |
| D | mbedtls.doxyfile | 3 # This file describes the settings to be used by the documentation system
29 # to put quotes around the project name if it contains spaces.
33 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
48 # Doxygen will copy the logo to the output directory.
52 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
54 # If a relative path is entered, it will be relative to the location
59 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
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.
81 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
[all …]
|
| /openthread-3.6.0/doc/ |
| D | Doxyfile.in | 15 # names of its contributors may be used to endorse or promote products
32 # This file describes the settings to be used by the
72 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
87 # to the output directory.
91 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
93 # entered, it will be relative to the location where doxygen was started. If
98 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
108 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
110 # information to generate all constant output in the proper language.
123 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
[all …]
|
| /openthread-3.6.0/third_party/jlink/SEGGER_RTT_V640/ |
| D | README.txt | 8 … - Main_RTT_MenuApp.c - Sample application to demonstrate RTT bi-directional functionality.
9 - Main_RTT_PrintfTest.c - Sample application to test RTT small printf implementation.
15 …- SEGGER_RTT_Printf.c - Simple implementation of printf to write formatted strings via RTT.
17 … - RTT_Syscalls_GCC.c - Low-level syscalls to retarget printf() to RTT with GCC / Newlib.
18 … - RTT_Syscalls_IAR.c - Low-level syscalls to retarget printf() to RTT with IAR compiler.
19 …- RTT_Syscalls_KEIL.c - Low-level syscalls to retarget printf() to RTT with KEIL/uVision c…
20 …- RTT_Syscalls_SES.c - Low-level syscalls to retarget printf() to RTT with SEGGER Embedde…
|
| /openthread-3.6.0/tools/harness-simulation/posix/etc/ |
| D | server.patch | 4 …systemctl is-active avahi-daemon || sudo systemctl start avahi-daemon || die 'Failed to start avah…
5 …|| systemctl is-active otbr-web || sudo systemctl start otbr-web || die 'Failed to start otbr-web!'
6 …systemctl is-active otbr-agent || sudo systemctl start otbr-agent || die 'Failed to start otbr-age…
7 + systemctl is-active commissionerd || sudo systemctl start commissionerd || die 'Failed to …
9 sudo service rsyslog status || sudo service rsyslog start || die 'Failed to start rsyslog!'
10 sudo service dbus status || sudo service dbus start || die 'Failed to start dbus!'
12 …sudo service avahi-daemon status || sudo service avahi-daemon start || die 'Failed to start avahi!'
13 …sudo service otbr-agent status || sudo service otbr-agent start || die 'Failed to start otbr-agent…
14 …I || sudo service otbr-web status || sudo service otbr-web start || die 'Failed to start otbr-web!'
15 + sudo service commissionerd status || sudo service commissionerd start || die 'Failed to st…
[all …]
|
| /openthread-3.6.0/tools/harness-simulation/ |
| D | README.md | 3 …ch is used by the Thread Test Harness Software to control OpenThread-based reference devices accor…
5 …ass template `ISniffer`, which is used by the Thread Test Harness Software to sniff all packets se…
7 …d simulation and sniffer simulation are required to run on a POSIX environment. However, Harness h…
9 Platform developers should modify the THCI implementation and/or the SI implementation directly to …
15 … `ot_path` to the absolute path where the top directory of the OpenThread repository is located. F…
16 …- For each entry in `ot_build.ot`, update the value of `number` to be the number of OT FTD simulat…
17 …- For each entry in `ot_build.otbr`, update the value of `number` to be the number of OTBR simulat…
18 - The numbers above can be adjusted according to the requirement of test cases.
19 …- Edit the value of `ssh.username` to the username to be used for connecting to the remote POSIX e…
20 - Edit the value of `ssh.password` to the password corresponding to the username above.
[all …]
|
| /openthread-3.6.0/third_party/mbedtls/repo/docs/ |
| D | getting_started.md | 21 …to design security into both hardware and firmware consistently. Part of the API provided by PSA i…
44 **Prerequisites to building the library with the provided makefiles:**
47 * Python 2 or Python 3 (either works) to generate the test code.
48 * Perl to run the tests.
50 If you have a C compiler such as GCC or Clang, just run `make` in the top-level directory to build …
52 …rent compiler, set the `CC` variable to the name or path of the compiler and linker (default: `cc`…
56 … makefiles pass options to the compiler that assume a GCC-like command line syntax. To use a diffe…
58 …you are cross-compiling, copy the test executable from the `tests` directory to the target machine.
66 To use a key for cryptography operations in Mbed Crypto, you need to first
70 **Prerequisites to importing keys:**
[all …]
|
| D | use-psa-crypto.md | 13 `MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER` to be disabled.
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
30 this requires changes to the application code for the (X.509 and) TLS layers
31 to pick up the improvements.
35 meaning that no changes to the application code are required for the TLS (and
36 X.509) layers to pick up the improvements.
40 There is a new API function `mbedtls_pk_setup_opaque()` that can be used to
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
[all …]
|
| /openthread-3.6.0/tools/harness-thci/ |
| D | README.md | 3 …ch is used by the Thread Test Harness Software to control OpenThread-based reference devices accor…
10 …to match their platform (for example, serial baud rate). Alternatively, platform developers may fo…
14 1. Copy "OpenThread.png" to `C:\GRL\Thread1.1\Web\images`.
16 2. Copy "deviceInputFields.xml" to `C:\GRL\Thread1.1\Web\data`.
18 3. Copy "OpenThread.py" to `C:GRL\Thread1.1\Thread_Harness\THCI`.
20 …iffer, and CC2538DK (or other hardware running OpenThread, as the reference device) to the Host PC.
24 6. Drag the "OpenThread: TI CC2538DK" reference device to the **Test Bed** section with the desired…
26 7. Select one or more test cases to execute.
30 1. Copy "OpenThread_WpanCtl.png" to `C:\GRL\Thread1.1\Web\images`.
32 2. Copy "deviceInputFields.xml" to `C:\GRL\Thread1.1\Web\data`.
[all …]
|
| /openthread-3.6.0/third_party/mbedtls/repo/ |
| D | CONTRIBUTING.md | 3 …ons from the community. There are some requirements we need to fulfill in order to be able to inte…
5 … will be reviewed by the project team and community and may need some modifications to be accepted.
10 - We would ask that contributions conform to [our coding standards](https://tls.mbed.org/kb/develop…
18 1. Fork the [Mbed TLS repository on GitHub](https://github.com/ARMmbed/mbedtls) to start making you…
21 …feature or topic. The larger the contribution is, the longer it would take to review it and merge …
23 …t one `Signed-off-by:` line from the committer. If anyone else contributes to the commit, they sho…
28 …to minimise the impact on users upgrading to newer versions of the library and it should not be ne…
30 …to users, where a change to the interface is required, all changes to the ABI or API, even on the …
32 …to an existing interface are necessary, functions in the public interface which need to be changed…
34 …to warn a user that the function will be removed at some point in the future, notifying users that…
[all …]
|
| D | README.md | 22 To generate a local copy of the library documentation in HTML format, tailored to your compile-time…
39 …velopment are CMake and GNU Make. Those systems are always complete and up-to-date. The others sho…
41 …x509 depends on libmbedcrypto. As a result, some linkers will expect flags to be in a specific ord…
45 You need the following tools to build the library with the provided makefiles:
49 * Python 3 to generate the test code.
50 * Perl to run the tests.
56 …to keep them as simple and independent of different toolchains as possible, to allow users to more…
58 In order to build from the source code using GNU Make, just enter at the command line:
62 In order to run the tests, enter:
66 The tests need Python to be built and Perl to be run. If you don't have one of them installed, you …
[all …]
|
| D | ChangeLog | 17 signing. It was intended to facilitate the transition in environments
31 MBEDTLS_CHECK_RETURN_WARNING to get warnings for other functions. This
33 extended to other modules in the future.
40 * Zeroize several intermediate variables used to calculate the expected
44 man-in-the-middle to inject fake ciphertext into a DTLS connection.
52 and mbedtls_ssl_free() would cause an internal session buffer to
57 * The GNU makefiles invoke python3 in preference to python except on Windows.
85 PSA_ALG_RSA_PSS_ANY_SALT to accept any salt length. Fixes #4946.
93 not to list other shared libraries they need.
101 pkcs12 functions when the password is empty. Fix the documentation to
[all …]
|
| D | LICENSE | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|
| /openthread-3.6.0/third_party/mbedtls/repo/docs/proposed/ |
| D | psa-driver-integration-guide.md | 6 This document describes how to build Mbed TLS with additional cryptoprocessor drivers that follow t…
12 …e provides a way to build Mbed TLS with additional code that implements certain cryptographic prim…
16 …N format and some code to include in the build. The driver code can either be provided in binary f…
18 ## How to build Mbed TLS with drivers
25 cd /path/to/mbedtls
32 cd /path/to/mbedtls
33 make PSA_DRIVERS="/path/to/acme/driver.json /path/to/nadir/driver.json" lib
39 cd /path/to/application
40 …ld myapp.o -L/path/to/acme -lacmedriver -L/path/to/nadir -lnadirdriver -L/path/to/mbedtls -lmbedcr…
|
| D | psa-conditional-inclusion-c.md | 4 This document is a proposed interface for deciding at build time which cryptographic mechanisms to …
12 …use case, it is often desirable to include only a subset of the available cryptographic mechanisms…
14 The present document proposes a way for an application using the PSA cryptography interface to decl…
18 …to select which cryptographic mechanisms are included in a build through its configuration file (`…
24 …to adapt to the PSA interface for several reasons. The `MBEDTLS_xxx_ALT` symbols are somewhat inco…
34 …he build does not require tools other than a C compiler. This is necessary to allow building an ap…
40 … and a block permutation (AES, CAMELLIA, ARIA, …), there is no requirement to include only specifi…
42 …ctions (for example encrypt/decrypt, sign/verify), there is no requirement to include only one dir…
44 [Limitation.size] There is no requirement to include only support for certain key sizes.
46 …] Where there are multiple ways to perform an operation, for example single-part and multi-part, t…
[all …]
|
| /openthread-3.6.0/tools/spi-hdlc-adapter/ |
| D | README.md | 14 …l for HDLC input/output. The path of the newly-created PTY will be written to `stdout`, followed b…
15 - `--raw`: Do not encode/decode packets using HDLC. Instead, write whole, raw frames to the specifi…
17 …: Specify a path to the Linux sysfs-exported GPIO directory for the `I̅N̅T̅` pin. If not specified…
18 - `--gpio-reset[=gpio-path]`: Specify a path to the Linux sysfs-exported GPIO directory for the `R̅…
19 - `--spi-mode[=mode]`: Specify the SPI mode to use (0-3). Default value is `0`.
21 … microseconds. Default is 20µs. Note that this may need to be set to zero for spi-hdlc-adapter to …
22 …to clip from start of MISO frame. This makes this tool usable with SPI slaves which have buggy SPI…
23 …r than or equal to this size will require only a single SPI transaction to be successfully transmi…
25 - `--help`: Print out usage information to `stdout` and exit.
27 `spi-device-path` is a required argument since it indicates which SPI device to use. An example pat…
[all …]
|
| /openthread-3.6.0/third_party/tcplp/bsdtcp/ |
| D | tcp_output.c | 121 struct tcpopt to; in tcp_output() local
729 to.to_flags = 0; in tcp_output()
734 to.to_mss = tcp_mssopt(tp); in tcp_output()
735 to.to_flags |= TOF_MSS; in tcp_output()
747 to.to_tfo_len = TCP_FASTOPEN_COOKIE_LEN; in tcp_output()
748 to.to_tfo_cookie = in tcp_output()
750 to.to_flags |= TOF_FASTOPEN; in tcp_output()
753 to.to_tfo_len = in tcp_output()
755 to.to_tfo_cookie = in tcp_output()
757 to.to_flags |= TOF_FASTOPEN; in tcp_output()
[all …]
|
| D | tcp_input.c | 466 struct tcpopt to; /* options in this segment */ in tcp_input() local
469 to.to_flags = 0; in tcp_input()
783 tcp_dooptions(&to, optp, optlen, TO_SYN); in tcp_input()
791 (to.to_flags & TOF_FASTOPEN)) { in tcp_input()
807 to.to_tfo_cookie, to.to_tfo_len, in tcp_input()
871 if (/*sc->sc_flags & SCF_WINSCALE*/to.to_flags & TOF_SCALE) { in tcp_input()
909 tp->snd_scale = /*sc->sc_requested_s_scale*/to.to_wscale; in tcp_input()
912 if (/*sc->sc_flags & SCF_TIMESTAMP*/to.to_flags & TOF_TS) { in tcp_input()
914 tp->ts_recent = /*sc->sc_tsreflect*/to.to_tsval; in tcp_input()
930 if (/*sc->sc_flags & SCF_SACK*/ to.to_flags & TOF_SACKPERM) in tcp_input()
[all …]
|
| /openthread-3.6.0/ |
| D | CONTRIBUTING.md | 1 # Contributing to OpenThread
3 …for you to contribute to OpenThread and help make it even better than it is today! As a contributo…
26 If you would like to implement a new feature, please consider the scope of the new feature:
28 … implementation work is accepted by the community. This will also allow us to better coordinate ou…
54 …to this project must be accompanied by a Contributor License Agreement. You (or your employer) ret…
56 …lly only need to submit a CLA once, so if you've already submitted one (even if it was for a diffe…
75 # Add each modified file you'd like to include in the commit
86 …to submitting your pull request, you might want to do a few things to clean up your branch and mak…
88 If any commits have been made to the upstream main branch, you should rebase your development branc…
100 Now, it may be desirable to squash some of your smaller commits down into a small number of larger …
[all …]
|
| D | NOTICE | 5 guidelines and certification programs to promote the availability of compliant
11 Specification and does not convey the right to identify any final product as Thread
13 property rights relating to the Thread 1.3.0 Final Specification, ownership and
14 licenses of which are subject to the Thread Group’s IP Policies, and not this license.
16 The included copyright to the OpenThread code is subject to the license in the
18 No warranty or assurance is made with respect to additional rights that may be
19 required to implement this code.
|
| /openthread-3.6.0/third_party/mbedtls/repo/programs/ |
| D | README.md | 20 … for any of the supported public-key algorithms (RSA or ECC) and writes it to a file that can be u…
24 …writer.c): loads a PEM or DER public key or private key file and writes it to a new PEM or DER fil…
26 …pk_decrypt.c): loads a PEM or DER public/private key file and uses the key to encrypt/decrypt a sh…
28 …/pk_verify.c): loads a PEM or DER private/public key file and uses the key to sign/verify a short …
34 …crypt.c`](pkey/rsa_decrypt.c): loads an RSA public/private key and uses it to encrypt/decrypt a sh…
36 * [`pkey/rsa_genkey.c`](pkey/rsa_genkey.c): generates an RSA key and writes it to a file that can b…
38 …verify.c`](pkey/rsa_verify.c): loads an RSA private/public key and uses it to sign/verify a short …
40 …ss.c`](pkey/rsa_verify_pss.c): loads an RSA private/public key and uses it to sign/verify a short …
44 …This pair of programs illustrates how to set up a secure channel using RSA for authentication and …
50 * [`pkey/dh_genprime.c`](pkey/dh_genprime.c): shows how to use the bignum (`mpi`) interface to gene…
[all …]
|
| /openthread-3.6.0/tests/toranj/ |
| D | README_CLI.md | 8 - It can be used to simulate multiple nodes forming complex network topologies.
50 …eates a Thread node instance. It creates a sub-process to run `ot-cli-ftd` and provides methods to…
62 Note: You may need to run as `sudo` to allow log file to be written (i.e., use `sudo python` or `su…
66 `cli.Node()` provides methods matching different CLI commands, in addition to some helper methods f…
89 # Try to join an existing network as specified by `another_node`.
101 Method `allowlist_node()` can be used to add a given node to the allowlist of the device and enable…
104 # `node2` is added to the allowlist of `node1` and allowlisting is enabled on `node1`
110 …pt below shows how to create a 3-node network topology with `node1` and `node2` being routers, and…
141 …to run all test-cases, if any test fails, to help with debugging of the issue, the last 30 lines o…
165 …to enable verbose logging for all nodes. The default value of `cli.Node._VERBOSE` is determined fr…
[all …]
|
| /openthread-3.6.0/third_party/mbedtls/repo/docs/architecture/ |
| D | psa-crypto-implementation-structure.md | 6 …o/mbed-crypto/psa/#application-programming-interface) defines an interface to cryptographic operat…
8 … the Mbed TLS PSA Cryptography API implementation which is tightly related to the PSA driver inter…
15 …h complexity. The core and its dispatching to software and hardware implementations are consequent…
18 …eliverables for a driver to be included into the Mbed TLS PSA Cryptography implementation. This pr…
22 …does not perform on its own any cryptographic operation. The core relies on PSA drivers to actually
26 * checking PSA API arguments and translating them into valid arguments for the necessary calls to t…
27 * dispatching the cryptographic operations to the appropriate PSA drivers.
36 * of arguments for the call to the driver interface, ... */
40 /* Call to the driver interface */
46 * by the driver, finalization of the values to return to the caller,
[all …]
|
| /openthread-3.6.0/third_party/mbedtls/repo/docs/architecture/testing/ |
| D | invasive-testing.md | 7 The goal of this document is to identify areas where black-box testing is insufficient and to propo…
16 * [“Solutions”](#solutions) explains how we currently solve, or intend to solve, specific problems.
20 …pto/keystore and X.509 parts of the library are about. More work is needed to fully take TLS into …
24 Always follow these rules unless you have a good reason not to. If you deviate, document the ration…
34 In unit tests and in test programs, it's ok to include header files from `library/`. Do not define …
36 Sometimes it makes sense to have unit tests on functions that aren't part of the public API. Declar…
41 > /* This test file is specific to the ITS implementation in PSA Crypto
42 > * on top of stdio. It expects to know what the stdio name of a file is
49 > # and not expected to be raised any time soon) is less than the maximum
55 If the most practical way to test something is to add code to the product that is only useful for t…
[all …]
|
| /openthread-3.6.0/third_party/mbedtls/repo/tests/scripts/ |
| D | test_zeroize.gdb | 12 # Unless required by applicable law or agreed to in writing, software
20 # Run a test using the debugger to check that the mbedtls_platform_zeroize()
24 # hit, the debugger manually checks the contents to be zeroized and checks that
28 # seem to be a mechanism to reliably check whether the zeroize calls are being
30 # problem is that a compiler would typically remove what it considers to be
33 # reads and writes to variables (among other situations). It will then use this
34 # data structure to remove redundant code that does not have an impact on the
37 # memory that is not accessed later in the program, so removing the call to
39 # inserting a test after a call to mbedtls_platform_zeroize() to check whether
40 # the block of memory was correctly zeroed would force the compiler to not
|
| /openthread-3.6.0/third_party/mbedtls/repo/.github/ |
| D | pull_request_template.md | 2 …ach commit must have at least one `Signed-off-by:` line from the committer to certify that the con…
3 * This is just a template, so feel free to use/remove the unnecessary things
12 When there is a bug fix, it should be backported to all maintained and supported branches.
13 Changes do not have to be backported if:
15 - This PR contains changes in the API. If this is true, and there is a need for the fix to be backp…
35 ## Steps to test or reproduce
36 Outline the steps to test or reproduce the PR here.
|
