| /net-tools-3.4.0/ |
| D | radvd_slip.conf | 6 AdvSendAdvert on;
16 AdvOnLink on;
19 DeprecatePrefix on;
23 RemoveRoute on;
27 FlushRDNSS on;
31 FlushDNSSL on;
|
| D | radvd_native_posix.conf | 6 AdvSendAdvert on;
16 AdvOnLink on;
19 DeprecatePrefix on;
23 RemoveRoute on;
27 FlushRDNSS on;
31 FlushDNSSL on;
|
| D | README NAT.md | 1 # Create NAT and routing for Zephyr native network on Linux
10 Zephyr applications, when build on native_posix or various qemu targets,
14 In order to have networking with Zephyr, you need to configure IP address on linux kernel side,
74 # These spawn the shell and logs into a virtual serial port on /dev/pts/X
|
| /net-tools-3.4.0/libcoap/examples/contiki/ |
| D | radvd.conf.sample | 3 AdvSendAdvert on;
9 AdvOnLink on;
10 AdvAutonomous on;
11 AdvRouterAddr on;
|
| /net-tools-3.4.0/mbedtls-2.4.0/tests/data_files/dir4/ |
| D | Readme | 3 1. zero pathlen constraint on an intermediate CA (invalid)
8 2. zero pathlen constraint on the root CA (invalid)
13 3. nonzero pathlen constraint on the root CA (invalid)
18 4. nonzero pathlen constraint on an intermediate CA (invalid)
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 7. pathlen constraint on the root CA with maximum number of elements and a self signed certificate …
39 8. zero pathlen constraint on first intermediate CA (valid)
44 9. zero pathlen constraint on trusted root (valid)
|
| /net-tools-3.4.0/libcoap/ |
| D | CONTRIBUTE | 18 The used VCS for libcoap is Git, the main repository is living on GitHub.
19 You can clone (or fork directly on GitHub) on the repository site:
27 The build environment is grounded on the classical autotools, the GNU GCC and
37 on Sourceforge.
46 The archive of the list can be found on:
55 holding the point releases, all the development process is going on in the
58 repository on GitHub:
62 4. Working on the source
64 As one golden rule you should work on improvements within *your* own local
66 as local branch and then start on top on this branch your own branch. So
[all …]
|
| D | TODO | 1 This is a simple file for all kinds of stuff related on devlopment for
7 Serious -> No regression on the user side, more likly on the libcoap
15 -> Remove #ifdef HAVE_ASSERT_H and so on from the public headers.
18 -> Adding DTLS functions based on openssl
30 -> Adding some documentation for classical users on how to use the libcoap
|
| D | LICENSE.GPL | 45 software. If the software is modified by someone else and passed on, we
47 that any problems introduced by others will not reflect on the original
65 refers to any such program or work, and a "work based on the Program"
75 is covered only if its contents constitute a work based on the
77 Whether that is true depends on what the Program does.
81 conspicuously and appropriately publish on each copy an appropriate
91 of it, thus forming a work based on the Program, and copy and
111 does not normally print such an announcement, your work based on
120 on the Program, the distribution of the whole must be on the terms of
127 collective works based on the Program.
[all …]
|
| /net-tools-3.4.0/libcoap/examples/ |
| D | coap-client.txt.in | 13 coap-client - CoAP Client based on libcoap
25 the protocol CoAP (RFC 7252) using the URI given as argument on the
60 The port to listen on.
120 Query on localhost via the 'GET' method.
126 Quite the same, except on the resource '.well-known/core' on localhost.
130 echo -n "mode=on" | coap-client -m put \
133 Send text 'mode=on' to resource 'actuators/leds?color=r' on the endpoint with
142 application/octet-stream) into resource 'ck' on 'fec0::3' by usage of a token
160 Please report bugs on the mailing list for libcoap:
|
| D | coap-rd.txt.in | 13 coap-rd - A CoAP Resource Directory based on libcoap
30 Join specified multicast 'group' on startup.
33 The 'port' on the given address the server will be waitung for connections.
45 Let the server listen on localhost (port 5683).
83 Please report bugs on the mailing list for libcoap:
|
| D | coap-server.txt.in | 13 coap-server - CoAP Server based on libcoap
30 Join specified multicast 'group' on startup.
33 The 'port' on the given address the server will be waitung for connections.
45 Let the server listen on localhost (port 5683).
83 Please report bugs on the mailing list for libcoap:
|
| /net-tools-3.4.0/tinydtls-0.8.2/tests/ |
| D | dtls-server.c | 280 int on = 1; local
324 if (setsockopt(fd, SOL_SOCKET, SO_REUSEADDR, &on, sizeof(on) ) < 0) {
334 on = 1;
336 if (setsockopt(fd, IPPROTO_IPV6, IPV6_RECVPKTINFO, &on, sizeof(on) ) < 0) {
338 if (setsockopt(fd, IPPROTO_IPV6, IPV6_PKTINFO, &on, sizeof(on) ) < 0) {
|
| D | dtls-client.c | 348 int on = 1; local
438 if (setsockopt(fd, SOL_SOCKET, SO_REUSEADDR, &on, sizeof(on) ) < 0) {
448 on = 1;
450 if (setsockopt(fd, IPPROTO_IPV6, IPV6_RECVPKTINFO, &on, sizeof(on) ) < 0) {
452 if (setsockopt(fd, IPPROTO_IPV6, IPV6_PKTINFO, &on, sizeof(on) ) < 0) {
|
| /net-tools-3.4.0/mbedtls-2.4.0/ |
| D | ChangeLog | 8 sessions. "Nonce-Disrespecting Adversaries Practical Forgery Attacks on GCM in
39 * Fix for key exchanges based on ECDH-RSA or ECDH-ECDSA which weren't
41 * Fix for out-of-tree builds using CMake. Found by jwurzer, and fix based on
75 * Added optimization for code space for X.509/OID based on configured
141 SLOTH attack on TLS 1.2 server authentication (other attacks from the
164 * Fix potential heap corruption on Windows when
169 on untrusted input or write keys of untrusted origin. Found by Guido
171 * The X509 max_pathlen constraint was not enforced on intermediate
195 * Fix failures in MPI on Sparc(64) due to use of bad assembly code.
222 string of close to or larger than 1GB to exploit; on 64 bit machines, would
[all …]
|
| D | README.md | 7 mbed TLS should build out of the box on most systems. Some platform specific options are available …
26 - depending on the yotta target, features of mbed OS may be used in examples and tests
28 … and libmbedtls. Note that libmbedtls depends on libmbedx509 and libmbedcrypto, and libmbedx509 de…
32 …developed by mbed, and is the build system of mbed OS 16.03. To install it on your platform, pleas…
42 If, on the other hand, you already have a copy of mbed TLS from a source other than the yotta regis…
51 …ore building unless it has already been set globally. For more information on using yotta, please …
53 For more details on the yotta/mbed OS edition of mbed TLS, including example programs, please consu…
57 …ality, as a lot of `Make` features are not supported on all different implementations of Make or o…
77 …can override `CFLAGS` and `LDFLAGS` by setting them in your environment or on the make command lin…
79 …on your platform, you might run into some issues. Please check the Makefiles in `library/`, `progr…
[all …]
|
| /net-tools-3.4.0/libcoap/src/ |
| D | coap_io.c | 122 int on = 1; in coap_new_endpoint() local
130 if (setsockopt(sockfd, SOL_SOCKET, SO_REUSEADDR, &on, sizeof(on)) < 0) in coap_new_endpoint()
133 on = 1; in coap_new_endpoint()
136 if (setsockopt(sockfd, IPPROTO_IP, IP_PKTINFO, &on, sizeof(on)) < 0) in coap_new_endpoint()
141 if (setsockopt(sockfd, IPPROTO_IPV6, IPV6_RECVPKTINFO, &on, sizeof(on)) < 0) in coap_new_endpoint()
144 if (setsockopt(sockfd, IPPROTO_IPV6, IPV6_PKTINFO, &on, sizeof(on)) < 0) in coap_new_endpoint()
|
| /net-tools-3.4.0/tinydtls-0.8.2/sha2/ |
| D | README | 8 it has not yet been tested on very many other architectures,
30 STDIN or reads one or more files specified on the command line, and then
48 on 32-bit words, this implementation may be slower than an
66 header file (or in the sha2.c file in some cases), or on the command
78 Here are the available options. Read on below for a description of
111 By defining this either on the command line or in sha2.h or sha2.c,
115 to optimize things. For example, on the FreeBSD and Linux x86 systems
116 I tested things on (using gcc), when I optimized with just -O2 and
127 compiled and tested the sha2.c and sha2.h code on Apple's OS X (on
128 a PPC), FreeBSD 4.1.1 on Intel, Linux on Intel, FreeBSD on the Alpha,
[all …]
|
| /net-tools-3.4.0/mbedtls-2.4.0/tests/suites/ |
| D | test_suite_x509parse.data | 3 … \: C=NL, O=PolarSSL, CN=PolarSSL Server 1\nissued on \: 2011-02-12 14\:44\:06\nexpires o…
7 …name \: C=NL, O=PolarSSL, CN=localhost\nissued on \: 2011-02-12 14\:44\:06\nexpires o…
11 … \: C=NL, O=PolarSSL, CN=PolarSSL Test CA\nissued on \: 2011-02-12 14\:44\:00\nexpires o…
15 … \: C=NL, O=PolarSSL, CN=PolarSSL Cert MD2\nissued on \: 2009-07-12 10\:56\:59\nexpires o…
19 … \: C=NL, O=PolarSSL, CN=PolarSSL Cert MD4\nissued on \: 2011-02-12 14\:44\:07\nexpires o…
23 … \: C=NL, O=PolarSSL, CN=PolarSSL Cert MD5\nissued on \: 2011-02-12 14\:44\:07\nexpires o…
27 … \: C=NL, O=PolarSSL, CN=PolarSSL Cert SHA1\nissued on \: 2011-02-12 14\:44\:07\nexpires o…
31 …: C=NL, O=PolarSSL, CN=PolarSSL Cert SHA224\nissued on \: 2011-02-12 14\:44\:07\nexpires o…
35 …: C=NL, O=PolarSSL, CN=PolarSSL Cert SHA256\nissued on \: 2011-02-12 14\:44\:07\nexpires o…
39 …: C=NL, O=PolarSSL, CN=PolarSSL Cert SHA384\nissued on \: 2011-02-12 14\:44\:07\nexpires o…
[all …]
|
| D | helpers.function | 257 * Although predictable and often similar on multiple
258 * runs, this does not result in identical random on
260 * test depend on the random data that is generated.
306 * This function returns random based on a buffer it receives.
310 * The number of bytes released from the buffer on each call to
355 * This function returns random based on a pseudo random function.
356 * This means the results should be identical on all systems.
357 * Pseudo random is based on the XTEA encryption algorithm to
|
| D | test_suite_asn1write.function | 33 /* Check for buffer overwrite on both sides */
69 /* Check for buffer overwrite on both sides */
106 /* Check for buffer overwrite on both sides */
|
| /net-tools-3.4.0/mbedtls-2.4.0/yotta/data/example-hashing/ |
| D | README.md | 11 …, listed in the [installation instructions](http://armmbed.github.io/yotta/#installing-on-windows).
21 …omputer with the micro-USB cable, being careful to use the "OpenSDA" connector on the target board.
47 7. Press the Reset button on the board.
54 {{description;mbed TLS example on hashing}}
|
| /net-tools-3.4.0/mbedtls-2.4.0/yotta/data/example-authcrypt/ |
| D | README.md | 11 …, listed in the [installation instructions](http://armmbed.github.io/yotta/#installing-on-windows).
21 …omputer with the micro-USB cable, being careful to use the "OpenSDA" connector on the target board.
47 7. Press the Reset button on the board.
68 The actual output for the ciphertext line will vary on each run because of the use of a random nonc…
|
| /net-tools-3.4.0/mbedtls-2.4.0/yotta/data/example-selftest/ |
| D | README.md | 3 …ponents. It serves as a basic sanity check to verify operation of mbed TLS on your platform. In th…
11 …, listed in the [installation instructions](http://armmbed.github.io/yotta/#installing-on-windows).
21 …omputer with the micro-USB cable, being careful to use the "OpenSDA" connector on the target board.
47 7. Press the Reset button on the board.
|
| /net-tools-3.4.0/mbedtls-2.4.0/yotta/data/example-benchmark/ |
| D | README.md | 11 …, listed in the [installation instructions](http://armmbed.github.io/yotta/#installing-on-windows).
21 …omputer with the micro-USB cable, being careful to use the "OpenSDA" connector on the target board.
47 7. Press the Reset button on the board.
96 …ion are indicative only of the performance of the mbed TLS module on the platform it's executed on.
|
| /net-tools-3.4.0/mbedtls-2.4.0/configs/ |
| D | README.txt | 3 The examples are generally focused on a particular usage case (eg, support for
11 (Depending on your compiler, you may need to ajust the line with
|
