Searched refs:in (Results 1 – 25 of 69) sorted by relevance
123
| /net-tools-3.4.0/ |
| D | README.legacy | 1 The comments and instructions below are for legacy IP stack in Zephyr.
6 tunslip6 can be used in host side to create a tun device that
19 set CONFIG_NETWORKING_UART=y in your configuration.
22 driver is not found in your default platform.
62 to work, you need to run radvd or similar tool in host side.
63 There is an example radvd.conf file present in the tools directory.
71 tunslip if for IPv4 networks and it can be used in host side
84 set CONFIG_NETWORKING_UART=y in your configuration.
87 driver is not found in your default platform.
106 echo-client is a tool that is run in Linux host side and
[all …]
|
| D | README.md | 5 The comments and instructions below are for the new IP stack in Zephyr.
34 Minimally you need these settings active in your project config file.
53 If your have echo-server running in the Qemu, then you can use the echo-client
54 tool in net-tools directory to communicate with it.
65 If building with CONFIG_NET_TCP=y in your project config file, it's possible
66 to run the echo-server sample in Zephyr, and then test the TCP stack using
77 that's only available in this version (wrapper around if_nametoindex(3)).
133 Finally run the stunnel script in Linux
142 If you are running echo-client in Zephyr QEMU, then run echo-server like
148 If you want to re-create the certificates in echo-server and echo-client in
[all …]
|
| /net-tools-3.4.0/mbedtls-2.4.0/ |
| D | ChangeLog | 7 with RFC-5116 and could lead to session key recovery in very long TLS
8 sessions. "Nonce-Disrespecting Adversaries Practical Forgery Attacks on GCM in
11 * Fixed potential stack corruption in mbedtls_x509write_crt_der() and
13 without checking whether there is enough space in the destination. The
21 * Added a script to print build environment info for diagnostic use in test
28 * Added the macro MBEDTLS_ENTROPY_MIN_HARDWARE in config.h. This allows users
36 * Fix dependency issue in Makefile to allow parallel builds.
37 * Fix incorrect handling of block lengths in crypt_and_hash.c sample program,
45 * Fix conditional statement that would cause a 1 byte overread in
52 * Fix mbedtls_x509_get_sig() to update the ASN1 type in the mbedtls_x509_buf
[all …]
|
| D | README.md | 7 …in the fully documented configuration file `include/mbedtls/config.h`, which is also the place whe…
21 …ays complete and up-to-date. The others should reflect all changes present in the CMake and Make b…
26 - depending on the yotta target, features of mbed OS may be used in examples and tests
28 …epends on libmbedcrypto. As a result, some linkers will expect flags to be in a specific order, fo…
46 …rom the root mbed TLS project directory. This will create the yotta module in the `yotta/module` d…
57 …, the Makefiles sometimes require some manual changes or export statements in order to work for yo…
75 …he build environment is a Windows shell (for instance using mingw32-make) (in that case some targe…
77 …in your environment will build shared libraries in addition to the static libraries. Setting `DEBU…
79 Depending on your platform, you might run into some issues. Please check the Makefiles in `library/…
108 - Release. This generates the default code without any unnecessary information in the binary file…
[all …]
|
| D | apache-2.0.txt | 36 "Work" shall mean the work of authorship, whether in Source or
38 copyright notice that is included in or attached to the work
39 (an example is provided in the Appendix below).
41 "Derivative Works" shall mean any work, whether in Source or Object
52 submitted to Licensor for inclusion in the Work by the copyright owner
61 designated in writing by the copyright owner as "Not a Contribution."
72 Work and such Derivative Works in Source or Object form.
77 (except as stated in this section) patent license to make, have made,
84 cross-claim or counterclaim in a lawsuit) alleging that the Work
91 Work or Derivative Works thereof in any medium, with or without
[all …]
|
| D | LICENSE | 1 Unless specifically indicated otherwise in a file, files are licensed
2 under the Apache 2.0 license, as can be found in: apache-2.0.txt
|
| /net-tools-3.4.0/mbedtls-2.4.0/tests/suites/ |
| D | test_suite_cipher.arc4.data | 61 ARC4 Encrypt and decrypt 0 bytes in multiple parts
65 ARC4 Encrypt and decrypt 1 bytes in multiple parts 1
69 ARC4 Encrypt and decrypt 1 bytes in multiple parts 2
73 ARC4 Encrypt and decrypt 16 bytes in multiple parts 1
77 ARC4 Encrypt and decrypt 16 bytes in multiple parts 2
81 ARC4 Encrypt and decrypt 16 bytes in multiple parts 3
85 ARC4 Encrypt and decrypt 16 bytes in multiple parts 4
89 ARC4 Encrypt and decrypt 22 bytes in multiple parts 1
93 ARC4 Encrypt and decrypt 22 bytes in multiple parts 1
97 ARC4 Encrypt and decrypt 22 bytes in multiple parts 1
[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
85 NULL Encrypt and decrypt 22 bytes in multiple parts 1
89 NULL Encrypt and decrypt 22 bytes in multiple parts 1
93 NULL Encrypt and decrypt 32 bytes in multiple parts 1
|
| D | test_suite_cipher.camellia.data | 301 CAMELLIA Encrypt and decrypt 0 bytes in multiple parts
305 CAMELLIA Encrypt and decrypt 1 bytes in multiple parts 1
309 CAMELLIA Encrypt and decrypt 1 bytes in multiple parts 2
313 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 1
317 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 2
321 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 3
325 CAMELLIA Encrypt and decrypt 16 bytes in multiple parts 4
329 CAMELLIA Encrypt and decrypt 22 bytes in multiple parts 1
333 CAMELLIA Encrypt and decrypt 22 bytes in multiple parts 1
337 CAMELLIA Encrypt and decrypt 22 bytes in multiple parts 1
[all …]
|
| D | test_suite_cipher.gcm.data | 61 AES 128 GCM Encrypt and decrypt 0 bytes in multiple parts
65 AES 128 GCM Encrypt and decrypt 1 bytes in multiple parts 1
69 AES 128 GCM Encrypt and decrypt 1 bytes in multiple parts 2
73 AES 128 GCM Encrypt and decrypt 16 bytes in multiple parts 1
77 AES 128 GCM Encrypt and decrypt 16 bytes in multiple parts 2
81 AES 128 GCM Encrypt and decrypt 22 bytes in multiple parts 1
85 AES 128 GCM Encrypt and decrypt 22 bytes in multiple parts 2
89 AES 128 GCM Encrypt and decrypt 32 bytes in multiple parts 1
189 AES 192 GCM Encrypt and decrypt 0 bytes in multiple parts
193 AES 192 GCM Encrypt and decrypt 1 bytes in multiple parts 1
[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
|
| D | test_suite_cipher.blowfish.data | 301 BLOWFISH Encrypt and decrypt 0 bytes in multiple parts
305 BLOWFISH Encrypt and decrypt 1 bytes in multiple parts 1
309 BLOWFISH Encrypt and decrypt 1 bytes in multiple parts 2
313 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 1
317 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 2
321 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 3
325 BLOWFISH Encrypt and decrypt 16 bytes in multiple parts 4
329 BLOWFISH Encrypt and decrypt 22 bytes in multiple parts 1
333 BLOWFISH Encrypt and decrypt 22 bytes in multiple parts 1
337 BLOWFISH Encrypt and decrypt 22 bytes in multiple parts 1
[all …]
|
| D | test_suite_cipher.des.data | 301 DES Encrypt and decrypt 0 bytes in multiple parts
305 DES Encrypt and decrypt 1 bytes in multiple parts 1
309 DES Encrypt and decrypt 1 bytes in multiple parts 2
313 DES Encrypt and decrypt 16 bytes in multiple parts 1
317 DES Encrypt and decrypt 16 bytes in multiple parts 2
321 DES Encrypt and decrypt 16 bytes in multiple parts 3
325 DES Encrypt and decrypt 16 bytes in multiple parts 4
329 DES Encrypt and decrypt 22 bytes in multiple parts 1
333 DES Encrypt and decrypt 22 bytes in multiple parts 1
337 DES Encrypt and decrypt 22 bytes in multiple parts 1
[all …]
|
| D | test_suite_cipher.aes.data | 305 AES Encrypt and decrypt 0 bytes in multiple parts
309 AES Encrypt and decrypt 1 bytes in multiple parts 1
313 AES Encrypt and decrypt 1 bytes in multiple parts 2
317 AES Encrypt and decrypt 16 bytes in multiple parts 1
321 AES Encrypt and decrypt 16 bytes in multiple parts 2
325 AES Encrypt and decrypt 16 bytes in multiple parts 3
329 AES Encrypt and decrypt 16 bytes in multiple parts 4
333 AES Encrypt and decrypt 22 bytes in multiple parts 1
337 AES Encrypt and decrypt 22 bytes in multiple parts 1
341 AES Encrypt and decrypt 22 bytes in multiple parts 1
[all …]
|
| /net-tools-3.4.0/mbedtls-2.4.0/yotta/data/ |
| D | README.md | 3 …ally easy for developers to include cryptographic and SSL/TLS capabilities in their embedded produ…
17 …b/development/yotta/data/example-selftest) Tests different basic functions in the mbed TLS library.
19 …le-benchmark) Measures the time taken to perform basic cryptographic functions used in the library.
25 …d mbed TLS. Each of them comes with complete usage instructions as a Readme file in the repository.
29 A high-level API for performing TLS and DTLS connections with mbed TLS in mbed OS is provided in a …
37 The list of available compilation flags is available in the fully documented [config.h file](https:…
39 …in your application's include directory, and can be named freely; you just need to let mbed TLS kn…
41 …in an application called `myapp`, if you want to enable the EC J-PAKE key exchange and disable the…
56 Please note: you need to provide the exact name that will be used in the `#include` directive, incl…
60 Like most components of mbed OS, mbed TLS is developed in the open and its source can be found on G…
[all …]
|
| /net-tools-3.4.0/tinydtls-0.8.2/sha2/ |
| D | README | 9 big-endian machines in particular.
21 hash algorithms as described in the PDF document found at the following
26 The interface is similar to the interface to SHA-1 found in the OpenSSL
39 * Input data is only accepted in octet-length increments. No sub-byte
42 accept message data in multiples of bytes.
54 * This implementation was written in C in hopes of portability and for
65 Each of the options described below may either be defined in the sha2.h
66 header file (or in the sha2.c file in some cases), or on the command
91 included in the inttypes.h header file. Those wanting to use inttypes.h
92 need to define this either in sha.h or at compile time.
[all …]
|
| /net-tools-3.4.0/tinydtls-0.8.2/doc/ |
| D | Doxyfile.in | 17 # This tag specifies the encoding used for all characters in the config file
44 # 4096 sub-directories (in 2 levels) under the output directory of each output
47 # source files, where putting all generated files in the same directory would
52 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
54 # information to generate all constant output in the proper language.
66 # include brief member descriptions after the members that are listed in
80 # that is used to form the text in various listings. Each string
81 # in this list, if found as the leading text of the brief description, will be
98 # inherited members of a class in the documentation of that class as if those
105 # path before files name in the file list and in the header files. If set
[all …]
|
| /net-tools-3.4.0/mbedtls-2.4.0/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 …]
|
| /net-tools-3.4.0/libcoap/doc/ |
| D | Doxyfile.in | 6 # All text after a double hash (##) is considered a comment and is placed in
20 # This tag specifies the encoding used for all characters in the config file
31 # project for which the documentation is generated. This name is used in the
32 # title of most generated pages and in a few other places.
49 # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
[all …]
|
| /net-tools-3.4.0/mbedtls-2.4.0/tests/data_files/dir4/ |
| D | Readme | 23 5. nonzero pathlen constraint on an intermediate CA with maximum number of elements in the chain (v…
28 6. nonzero pathlen constraint on the root CA with maximum number of elements in the chain (valid)
33 … on the root CA with maximum number of elements and a self signed certificate in the chain (valid)
34 …tes issued before the integration will have an intermadiate self signed certificate in their chain)
|
| /net-tools-3.4.0/mbedtls-2.4.0/yotta/data/example-benchmark/ |
| D | README.md | 11 …yotta). Please note that **yotta has its own set of dependencies**, listed in the [installation in…
15 …other board supported by mbed OS (in which case you'll have to substitute frdm-k64f-gcc with the a…
49 8. The output in the terminal window should look like:
98 …in the integration of mbed TLS into the platform, such as whether all available hardware accelerat…
100 The figures may also slightly change from execution to execution due to variations in the timing fu…
|
| /net-tools-3.4.0/libcoap/ |
| D | .gitignore | 6 Makefile.in
21 # warn about specific macros in the m4 directory if they missing
38 doc/Makefile.in
|
| /net-tools-3.4.0/mbedtls-2.4.0/yotta/data/example-authcrypt/ |
| D | README.md | 11 …yotta). Please note that **yotta has its own set of dependencies**, listed in the [installation in…
15 …other board supported by mbed OS (in which case you'll have to substitute frdm-k64f-gcc with the a…
49 8. The output in the terminal window should look like:
68 …ciphertext line will vary on each run because of the use of a random nonce in the encryption proce…
|
| /net-tools-3.4.0/systemd/ |
| D | README.rst | 7 have loop-socat.sh and loop-slip-tap.sh open in other terminals when you run
8 Zephyr in QEMU with networking.
14 user who is running Zephyr in QEMU. Therefore you need to create a zephyr user
|
| /net-tools-3.4.0/tinydtls-0.8.2/sha2/testvectors/testvectors/ |
| D | vector004.dat | 1 …in Liberty, and dedicated to the proposition that all men are created equal. Now we are engaged i…
|
123
