Searched refs:from (Results 1 – 25 of 60) sorted by relevance
123
| /net-tools-3.4.0/mbedtls-2.4.0/tests/suites/ |
| D | test_suite_mdx.data | 64 mbedtls_ripemd160 Test vector from paper #1
67 mbedtls_ripemd160 Test vector from paper #2
70 mbedtls_ripemd160 Test vector from paper #3
73 mbedtls_ripemd160 Test vector from paper #4
76 mbedtls_ripemd160 Test vector from paper #5
79 mbedtls_ripemd160 Test vector from paper #6
82 mbedtls_ripemd160 Test vector from paper #7
85 mbedtls_ripemd160 Test vector from paper #8
|
| D | test_suite_hmac_drbg.misc.data | 61 HMAC_DRBG from buffer SHA-1
65 HMAC_DRBG from buffer SHA-224
69 HMAC_DRBG from buffer SHA-256
73 HMAC_DRBG from buffer SHA-384
77 HMAC_DRBG from buffer SHA-512
|
| D | test_suite_dhm.data | 10 Diffie-Hallman load parameters from file
13 Diffie-Hallman load parameters from file
|
| /net-tools-3.4.0/docker/ |
| D | danted.conf | 8 from: 0.0.0.0/0 to: 0.0.0.0/0
12 from: 0.0.0.0/0 to: 0.0.0.0/0
|
| /net-tools-3.4.0/virtual-hub/ |
| D | README.md | 4 QEMU nodes running zephyr application. It receive packets from QEMU
39 to 1 on CMakeLists.txt from the target projects.
56 the connection matrix from `input.csv`. This way the first line and column
57 from the file refers to the node with `QEMU_PIPE_ID` defined with 1. In the
58 same way the second line and column from the file refers to the node with
|
| /net-tools-3.4.0/tinydtls-0.8.2/sha2/testvectors/testvectors/ |
| D | vector003.info | 2 For this test data (from the PDF document), no example output
4 provided), so the sample for SHA-256 comes from the output of
|
| D | vector016.info | 2 This test vector came from Brian LaMacchia in his e-mail
3 message containing several samples of output from his SHA-256
|
| D | vector004.info | 2 The output samples for this test vector come exclusively from my
4 a very large grain of salt. The input sample comes from...well
|
| D | vector001.info | 2 This test vector is taken from the PDF document that describes
|
| D | vector002.info | 4 output from my own implementation which may not be correct.
|
| D | vector014.info | 2 The output samples for thi test vector come exclusively from my
|
| D | vector008.info | 2 The output samples for thi test vector come exclusively from my
|
| D | vector010.info | 2 The output samples for thi test vector come exclusively from my
|
| D | vector012.info | 2 The output samples for thi test vector come exclusively from my
|
| D | vector006.info | 2 The output samples for thi test vector come exclusively from my
|
| D | vector007.info | 2 The output samples for thi test vector come exclusively from my
|
| D | vector004.dat | 1 …from these honored dead we take increased devotion to that cause for which they gave the last full…
|
| D | vector011.info | 2 The output samples for thi test vector come exclusively from my
|
| /net-tools-3.4.0/ |
| D | stunnel_sc.conf | 12 ; *:4242 - Listen encrypted traffic from Zephyr
13 ; *:4243 - Listen unencrypted traffic from localhost (client)
|
| D | stunnel.conf | 13 ; *:4242 - Listen encrypted traffic from Zephyr
14 ; *:4243 - Listen unencrypted traffic from localhost (client)
|
| D | echo-server.c | 193 struct sockaddr_in6 from = { 0 }; in udp_receive_and_reply() local
194 socklen_t fromlen = sizeof(from); in udp_receive_and_reply()
198 (struct sockaddr *)&from, &fromlen, proto); in udp_receive_and_reply()
206 (struct sockaddr *)&from, fromlen, proto); in udp_receive_and_reply()
220 struct sockaddr_in6 from = { 0 }; in tcp_receive_and_reply() local
221 socklen_t fromlen = sizeof(from); in tcp_receive_and_reply()
226 (struct sockaddr *)&from, &fromlen, proto); in tcp_receive_and_reply()
231 (struct sockaddr *)&from, fromlen, proto); in tcp_receive_and_reply()
|
| /net-tools-3.4.0/libcoap/examples/lwip/ |
| D | README | 17 * download lwip and lwip-contrib from the upstream git sources
26 differ from regular libcoap usage. If you seem to run out of memory creating
|
| /net-tools-3.4.0/libcoap/ |
| D | TODO | 14 -> Remove the #include "coap_config.h" directive from the public header files.
15 -> Remove #ifdef HAVE_ASSERT_H and so on from the public headers.
16 -> Use coap.h as the only header to include from the public view.
|
| /net-tools-3.4.0/python-websocket-server/ |
| D | README.md | 58 *`host`* - By default the `127.0.0.1` is used which allows connections only from the current machin…
75 … a callback function that will be called for every `client` disconnecting from us | function …
86 | `set_fn_client_left()` | Called for every `client` disconnecting from us | client, server …
96 from websocket_server import WebsocketServer
|
| /net-tools-3.4.0/mbedtls-2.4.0/ |
| D | README.md | 23 Yotta, as a build system, is slightly different from the other build systems:
34 Once yotta is installed, you can use it to download the latest version of mbed TLS from the yotta r…
42 …y have a copy of mbed TLS from a source other than the yotta registry, for example from cloning ou…
46 This should be executed from the root mbed TLS project directory. This will create the yotta module…
59 In order to build from the source code using Make, just enter at the command line:
75 …environment is Unix-like (for instance when cross-compiling, or compiling from an MSYS shell), and…
144 …te the tests files (e.g. `test\_suite\_mpi.c`). These files are generated from a `function file` (…
162 We gratefully accept bug reports and contributions from the community. There are some requirements …
168 …eloper.mbed.org/contributor_agreement/). Alternatively, for contributions from corporations, or th…
|
123
