Searched refs:shared (Results 1 – 25 of 29) sorted by relevance
12
/openthread-latest/third_party/mbedtls/repo/library/ |
D | Makefile | 228 .PHONY: all static shared clean 233 all: shared static 239 shared: libmbedcrypto.$(DLEXT) libmbedx509.$(DLEXT) libmbedtls.$(DLEXT) target 262 …$(CC) -shared -Wl,-soname,$@ -o $@ $(OBJS_TLS) -L. -lmbedx509 -lmbedcrypto $(LOCAL_LDFLAGS) $(LDFL… 276 …$(CC) -shared -Wl,-soname,$@ -Wl,--out-implib,$@.a -o $@ $(OBJS_TLS) -lws2_32 -lwinmm -lgdi32 -L. … 291 $(CC) -shared -Wl,-soname,$@ -o $@ $(OBJS_X509) -L. -lmbedcrypto $(LOCAL_LDFLAGS) $(LDFLAGS) 305 …$(CC) -shared -Wl,-soname,$@ -Wl,--out-implib,$@.a -o $@ $(OBJS_X509) -lws2_32 -lwinmm -lgdi32 -L.… 320 $(CC) -shared -Wl,-soname,$@ -o $@ $(OBJS_CRYPTO) $(LOCAL_LDFLAGS) $(LDFLAGS) 334 …$(CC) -shared -Wl,-soname,$@ -Wl,--out-implib,$@.a -o $@ $(OBJS_CRYPTO) -lws2_32 -lwinmm -lgdi32 -…
|
D | CMakeLists.txt | 2 option(USE_SHARED_MBEDTLS_LIBRARY "Build Mbed TLS shared library." OFF) 243 message(FATAL_ERROR "Need to choose static or shared mbedtls build!")
|
/openthread-latest/third_party/mbedtls/repo/tests/docker/bionic/ |
D | Dockerfile | 65 && ./config --openssldir=/usr/local/openssl-1.0.1j no-shared \ 75 && ./config --openssldir=/usr/local/openssl-1.0.2g no-shared \ 86 …./config --prefix=/usr/local/openssl-1.1.1a -Wl,--enable-new-dtags,-rpath,'${LIBRPATH}' no-shared \ 106 …=/usr/local/gnutls-3.3.8 --exec_prefix=/usr/local/gnutls-3.3.8 --disable-shared --disable-guile --… 129 --disable-shared --disable-guile --disable-doc \ 152 --disable-shared --disable-guile --disable-doc \
|
/openthread-latest/third_party/mbedtls/repo/docs/architecture/ |
D | psa-shared-memory.md | 1 PSA API functions and shared memory 6 …s that are in memory that is shared with an untrusted process. On such systems, the untrusted proc… 13 …erview/conventions.html#output-buffer-sizes). Any other data is assumed to be in non-shared memory. 21 …nments where the arguments passed to a PSA Crypto API function may be in shared memory (as opposed… 31 * a crypto service, which offers PSA crypto API calls over RPC (remote procedure call) using shared… 39 If an input argument is in shared memory, there is a risk of a **read-read inconsistency**: 45 …ithout validation. A malicious client can modify the length field in the shared memory between the… 54 If an output argument is in shared memory, there is a risk of a **write-read inconsistency**: 66 If an output argument is in shared memory, there is a risk of a **write-write disclosure**: 74 …shared key. Clients are not allowed to access each other's data. The provisioning application isol… [all …]
|
D | tls13-support.md | 22 - Mbed TLS supports pre-shared keys for key establishment, pre-shared keys 355 bypassed if the handshake is based on a pre-shared key and thus does not
|
D | mbed-crypto-storage-specification.md | 47 There is a shared namespace for all callers.
|
/openthread-latest/third_party/mbedtls/repo/3rdparty/p256-m/p256-m/ |
D | README.md | 199 shared bignum/MPI module (possibly also supporting RSA), which makes fair 222 | ECDH shared secret | 640 | 728 | 231 | ECDH shared secret | 596 | 700 | 245 | ECDH shared secret | 922 | 975 | 255 | ECDH shared secret | 144 | 177 | 265 | ECDH shared secret | 11 | 13 | 277 | ECDH shared secret | 1060 | 1611 | 284 - While p256-m fully validates all inputs, Tinycrypt's ECDH shared secret 400 byte arrays. Key generation and ECDH shared secret computation are thin 407 - ECDH shared secret computation
|
/openthread-latest/src/cli/ |
D | README_COMMISSIONING.md | 69 2. Add the Joiner with the device-specific pre-shared key (PSKd)
|
D | README_COAPS.md | 194 - psk: pre-shared key 195 - pskid: pre-shared key identifier
|
/openthread-latest/third_party/build_gn/toolchain/ |
D | BUILD.gn | 38 command = "g++ -shared {{ldflags}} -o $sofile -Wl,-soname=$soname @$rspfile"
|
/openthread-latest/third_party/mbedtls/repo/tests/suites/ |
D | test_suite_ecdh.function | 323 /* server computes shared secret */ 341 /* client computes shared secret */
|
D | test_suite_psa_crypto_pake.function | 867 /* Get shared key */
|
D | test_suite_ssl.function | 3792 "from the one associated with the pre-shared key."; 3800 "from the one associated with the pre-shared key.";
|
/openthread-latest/third_party/mbedtls/repo/ |
D | CMakeLists.txt | 300 # The C files in tests/src directory contain test code shared among test suites 301 # and programs. This shared test code is compiled and linked to test suites and
|
D | SECURITY.md | 53 by leveraging shared hardware that both Mbed TLS and the attacker have access
|
D | README.md | 109 Setting the variable `SHARED` in your environment will build shared libraries in addition to the st… 137 To configure CMake for building shared libraries, use:
|
D | ChangeLog | 154 the function call (i.e. no buffer parameters are in shared memory), 710 used on a shared secret from a key agreement since its input must be 753 * Fix TLS 1.3 session resumption when the established pre-shared key is 754 384 bits long. That is the length of pre-shared keys created under a 825 * make: enable building unversioned shared library, with e.g.: 862 * Mbed TLS now supports TLS 1.3 key establishment via pre-shared keys. 863 The pre-shared keys can be provisioned externally or via the ticket 1090 now capable of negotiating another shared secret if the one sent in its 1110 * Opaque pre-shared keys for TLS, provisioned with 1185 * Fix the library search path when building a shared library with CMake [all …]
|
/openthread-latest/third_party/mbedtls/repo/docs/ |
D | use-psa-crypto.md | 96 ### PSA-held (opaque) keys for TLS pre-shared keys (PSK)
|
D | psa-transition.md | 1111 …p__key__derivation_1ga90fdd2716124d0bd258826184824675f) to calculate the shared secret from your p… 1114 …04ec442db78745f) instead of `psa_raw_key_agreement` to use the resulting shared secret as the secr… 1125 …* `mbedtls_mpi z` for the shared secret (this may be the same variable as `our_priv` when doing ep… 1129 … (output), `their_pub` and `our_priv`. Use the raw shared secret `z`, typically, to construct a sh… 1144 …Alternatively, call `psa_key_derivation_key_agreement` to use the shared secret directly in a key … 1159 …, then call `mbedtls_ecdh_calc_secret` or `mbedtls_dhm_calc_secret` to calculate the shared secret. 1171 …Alternatively, call `psa_key_derivation_key_agreement` to use the shared secret directly in a key … 1183 4. Call `mbedtls_ecdh_calc_secret` or `mbedtls_dhm_calc_secret` to calculate the shared secret. 1194 …Alternatively, call `psa_key_derivation_key_agreement` to use the shared secret directly in a key … 1204 …the PSA API only uses the peer's public key to immediately calculate the shared secret. If your ap… [all …]
|
/openthread-latest/third_party/mbedtls/repo/programs/ |
D | README.md | 44 …ecure channel using RSA for authentication and Diffie-Hellman to generate a shared AES session key.
|
/openthread-latest/ |
D | CONTRIBUTING.md | 140 …ploaded as artifacts in a failed check. Besides core dumps, binaries and shared libraries are also…
|
D | STYLE_GUIDE.md | 6 …strained Systems and Shared Infrastructure](#tightly-constrained-systems-and-shared-infrastructure)
|
/openthread-latest/third_party/mbedtls/repo/docs/proposed/ |
D | psa-driver-interface.md | 558 1. Call the `"key_agreement_to_key"` entry point to create a key object containing the shared secre… 563 …raw_key_agreement()` followed by a call to `psa_key_derivation_input_bytes()` on the shared secret. 588 …attributes for the shared secret are not placed near the beginning, but rather grouped with the ot… 610 * `"pake_get_implicit_key"` (mandatory): returns implicitly confirmed shared secret from a PAKE.
|
/openthread-latest/third_party/mbedtls/repo/docs/architecture/psa-migration/ |
D | psa-legacy-bridges.md | 55 … scope of the legacy crypto APIs are trivial (ciphertexts, hashes, MACs, shared secrets). The one …
|
/openthread-latest/third_party/mbedtls/repo/docs/architecture/psa-thread-safety/ |
D | psa-thread-safety.md | 296 …r the operation, using their own operation-specific mutexes to guard any shared data that they use.
|
12