Searched refs:platform (Results 1 – 25 of 38) sorted by relevance
12
| /mbedtls-latest/docs/architecture/ |
| D | alternative-implementations.md | 4 … the Mbed TLS functionality can be replaced at compile time to integrate the library on a platform.
10 …to customize some aspects of how Mbed TLS interacts with the underlying platform. This section dis…
12 …platform module (`include/mbedtls/platform.h`) controls how Mbed TLS accesses standard library fea…
14 …dom generation, enabled with `MBEDTLS_ENTROPY_NV_SEED`, is also controlled via the platform module.
22 …pport alternative implementations. If this module does not work on your platform, disable `MBEDTLS…
24 If your platform has a cryptographic accelerator, you can use it via a [PSA driver](#psa-cryptograp…
34 …phy modules (symmetric algorithms, DHM, RSA, ECP, ECJPAKE) and for some platform-related modules (…
80 ### Alternative implementations of platform functions
82 Several platform functions can be reconfigured dynamically by following the process described here.…
91 …onsult the documentation of individual configuration options and of the platform module for detail…
|
| D | mbed-crypto-storage-specification.md | 99 * [PSA platform](#file-namespace-on-a-psa-platform-for-1.0.0)
131 ### File namespace on a PSA platform for 1.0.0
164 …platform integration use different sets of file names. This is annoyingly non-uniform. For example…
228 ### File namespace on a PSA platform on TBD
275 * For an opaque key (key in a secure element): slot number (8 bytes), in platform endianness.
282 All integers are encoded in platform endianness.
292 …platform): the internal representation of the key identifier. On a PSA platform, this encodes the …
335 * For an opaque key (key in a secure element): slot number (8 bytes), in platform endianness.
351 * [PSA platform](#file-namespace-on-a-psa-platform-on-mbed-tls-2.25.0)
367 ### File namespace on a PSA platform on Mbed TLS 2.25.0
[all …]
|
| /mbedtls-latest/tests/suites/ |
| D | host_test.function | 330 static const char *platform = NULL;
338 if (platform == NULL) {
339 platform = getenv("MBEDTLS_TEST_PLATFORM");
340 if (platform == NULL) {
341 platform = "unknown";
362 platform, configuration, test_suite, test_case);
470 /* No chdir() or no support for parsing argv[0] on this platform. */
529 * structures, which should work on every modern platform. Let's be sure.
|
| D | main_test.function | 223 * \brief Program main. Invokes platform specific execute_tests().
246 * Note that we do this before the platform setup (which may access
258 "FATAL: Failed to initialize platform - error %d\n",
|
| D | test_suite_net.function | 117 * this platform limitation.
121 * is problematic on the particular platform where the code is running,
|
| D | helpers.function | 22 #include "mbedtls/platform.h"
|
| D | test_suite_platform_printf.function | 12 #include "mbedtls/platform.h"
|
| D | test_suite_entropy.function | 439 /* Check if platform NV read and write manipulate the same data */
448 /* Check if platform NV write and raw read manipulate the same data */
|
| D | test_suite_platform.function | 73 * Windows CI reports random test fail on platform-suite. It might
|
| /mbedtls-latest/tests/git-scripts/ |
| D | README.md | 14 **Note: Currently the Mbed TLS git hooks work only on a GNU platform. If using a non-GNU platform, …
|
| /mbedtls-latest/ |
| D | README.md | 11 Mbed TLS should build out of the box on most systems. Some platform specific options are available …
63 …ripts and whose content depends only on the Mbed TLS source, not on the platform or on the library…
73 * A C compiler for the host platform, for some test data.
75 …you must set the `CC` environment variable to a C compiler for the host platform when generating t…
107 In order to build for a Windows platform, you should use `WINDOWS_BUILD=1` if the target is Windows…
113 …platform, you might run into some issues. Please check the Makefiles in `library/`, `programs/` an…
264 Mbed TLS is mostly written in portable C99; however, it has a few platform requirements that go bey…
279 …e (PSA)](https://developer.arm.com/architectures/security-architectures/platform-security-architec…
281 …platform to build services, such as secure boot, secure storage and secure communication. Second, …
|
| D | SECURITY.md | 77 The attacker code running on the platform has access to some sensor capable of
80 platform that is located unfortunately enough to pick up the CPU noise.
84 a user application's threat model, they need to be mitigated by the platform.
93 application's threat model, they need to be mitigated by the platform.
|
| D | ChangeLog | 129 building for linux platform.
282 * Add partial platform support for z/OS.
576 * AES performance improvements. Uplift varies by platform,
872 * Use platform-provided secure zeroization function where possible, such as
1207 * The library will no longer compile out of the box on a platform without
1208 setbuf(). If your platform does not have setbuf(), you can configure an
1323 * Add the platform function mbedtls_setbuf() to allow buffering to be
1822 C compiler for the host platform are required. See “Generated source files
2273 identical to psa_key_id_t instead of being platform-defined. This bridges
2490 in a platform header. Contributed by Abdelatif Guettouche in #3557.
[all …]
|
| /mbedtls-latest/programs/test/ |
| D | metatest.c | 366 const char *platform; member
455 mbedtls_printf("%s %s\n", p->name, p->platform); in main()
|
| /mbedtls-latest/docs/architecture/testing/ |
| D | invasive-testing.md | 71 …rary` directory such as `psa_crypto_invasive.h`. This is similar to the platform function configur…
88 * Portability: tests should work on every platform. Skipping tests on certain platforms may hide er…
147 …aces, with many platform functions that can be substituted (`MBEDTLS_PLATFORM_xxx` macros). PSA Cr…
178 …in the tests that are not necessarily always true (for example that are platform-specific). We may…
197 * This does not work for platform-dependent properties unless we have a formal model of the platfor…
201 | Coverage | ~ Good for platform-independent properties, if we can guarantee them statically |
|
| D | test-framework.md | 59 * **Platform**: a description of the platform, e.g. `Linux-x86_64` or `Linux-x86_64-gcc7-msan`.
|
| /mbedtls-latest/ChangeLog.d/ |
| D | 00README.md | 12 platform, etc.
13 * New features in the library, new sample programs, or new platform support.
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-developer-guide.md | 17 …certain cryptographic primitives. This is primarily intended to support platform-specific hardware.
34 * An object file compiled for the target platform defining the functions required by the driver des…
|
| D | psa-driver-integration-guide.md | 13 …certain cryptographic primitives. This is primarily intended to support platform-specific hardware.
|
| /mbedtls-latest/tests/scripts/ |
| D | run-metatests.sh | 6 Run all the metatests whose platform matches any of the given PLATFORM.
|
| /mbedtls-latest/scripts/ |
| D | windows_msbuild.bat | 4 … https://docs.microsoft.com/en-us/cpp/build/how-to-modify-the-target-framework-and-platform-toolset
|
| /mbedtls-latest/scripts/data_files/ |
| D | error.fmt | 16 #include "mbedtls/platform.h"
|
| D | query_config.fmt | 12 #include "mbedtls/platform.h"
|
| /mbedtls-latest/scripts/data_files/driver_templates/ |
| D | psa_crypto_driver_wrappers_no_static.c.jinja | 22 #include "mbedtls/platform.h"
|
| /mbedtls-latest/library/ |
| D | Makefile | 139 platform.o \
|
12
