| /mbedtls-3.6.0/tests/suites/ |
| D | test_suite_md.psa.data | 5 PSA dispatch MD5 legacy only
9 PSA dispatch MD5 driver only
17 PSA dispatch RIPEMD160 legacy only
21 PSA dispatch RIPEMD160 driver only
29 PSA dispatch SHA1 legacy only
33 PSA dispatch SHA1 driver only
41 PSA dispatch SHA224 legacy only
45 PSA dispatch SHA224 driver only
53 PSA dispatch SHA256 legacy only
57 PSA dispatch SHA256 driver only
[all …]
|
| D | test_suite_bignum_core.generated.data | 9356 Core modular exponentiation (Mongtomery form only) #1 0 ^ 0 mod 53
9359 Core modular exponentiation (Mongtomery form only) #2 0 ^ 1 mod 53
9362 Core modular exponentiation (Mongtomery form only) #3 0 ^ 2 mod 53
9365 Core modular exponentiation (Mongtomery form only) #4 0 ^ 3 mod 53
9368 Core modular exponentiation (Mongtomery form only) #5 0 ^ 4 mod 53
9371 Core modular exponentiation (Mongtomery form only) #6 0 ^ 38 mod 53
9374 Core modular exponentiation (Mongtomery form only) #7 0 ^ d1c127a667786703830500038ebaef20e5a3e2dc3…
9377 Core modular exponentiation (Mongtomery form only) #8 0 ^ 177219d30e7a269fd95bafc8f2a4d27bdcf4bb99f…
9380 Core modular exponentiation (Mongtomery form only) #9 0 ^ cf1822ffbc6887782b491044d5e341245c6e43371…
9383 Core modular exponentiation (Mongtomery form only) #10 0 ^ c93ba7ec74d96f411ba008bdb78e63ff11bb5df4…
[all …]
|
| /mbedtls-3.6.0/docs/ |
| D | driver-only-builds.md | 2 cryptographic mechanisms are provided only by PSA drivers (that is, no
17 In order to have some mechanism provided only by a driver, you'll want
30 In addition, for each mechanism you want provided only by your driver:
40 For example, if you want SHA-256 to be provided only by a driver, you'll want
46 driver-only mechanisms. Note that this is already a requirement for any use of
54 For now, only the following (families of) mechanisms are supported:
59 Supported means that when those are provided only by drivers, everything
69 you're interested in driver-only support for RSA, please let us know.
74 It is possible to have all hash operations provided only by a driver.
89 a hash algorithm that is provided only by a driver, as mentioned in [General
[all …]
|
| D | 3.0-migration-guide.md | 60 The only value supported by Mbed TLS 3.0.0 is `0x03000000`.
66 …new fields. Also, as before, some public fields should be considered read-only, since modifying th…
87 The file `include/mbedtls/net.h` was removed because its only function was to
92 This change does not affect users who use the default configuration; it only
110 This feature was only used in some classic (non-PSA) cryptography modules. It was
131 Alternatively, for testing purposes only, you can create and register a fake
139 This only affects users who called the HAVEGE modules directly (not
141 only source of entropy. If you're in that case, please declare OS or hardware
149 This only affects people who've been using Mbed TLS since before version 2.0
182 library, only in binary form) or RFC 7919 (also available in the library) or
[all …]
|
| /mbedtls-3.6.0/library/ |
| D | aesni.h | 6 * \warning These functions are only for internal use by other library
27 * (Only implemented with certain compilers, only for certain targets.)
31 /* Visual Studio supports AESNI intrinsics since VS 2008 SP1. We only support
35 /* GCC-like compilers: currently, we only support intrinsics if the requisite
53 * (Only implemented with gas syntax, only for 64-bit.)
71 * \note This function is only for internal use by other library
88 * \note This function is only for internal use by other library
106 * \note This function is only for internal use by other library
124 * \note This function is only for internal use by other library
138 * \note This function is only for internal use by other library
|
| D | psa_crypto_invasive.h | 4 * \brief PSA cryptography module: invasive interfaces for test only.
6 * The interfaces in this file are intended for testing purposes only.
29 * This function may only be called before a call to psa_crypto_init(),
33 * This function is only intended for test purposes. The functionality
|
| D | padlock.h | 7 * \warning These functions are only for internal use by other library
56 * \note This function is only for internal use by other library
68 * \note This function is only for internal use by other library
86 * \note This function is only for internal use by other library
|
| D | mps_reader.h | 57 * and producer mode, because it only interfaces with the reader
132 * and only if \c frag is not \c NULL. */
144 * This is only used when the reader is in
157 * This is only used when the reader is in
171 * This is only used when the reader is in
175 /* The accumulator is only needed if we need to be able to pause
198 * only used in producing mode.
206 * It is only used in consuming mode.
328 * progress is guaranteed only if the same amount of data
|
| /mbedtls-3.6.0/docs/proposed/ |
| D | psa-conditional-inclusion-c.md | 12 … implementation for a specific use case, it is often desirable to include only a subset of the ava…
18 …ility of an alternative implementation, so the software implementation is only included if `MBEDTL…
22 …only has partial support for the mechanism). **Opaque drivers** implement cryptographic mechanisms…
40 … permutation (AES, CAMELLIA, ARIA, …), there is no requirement to include only specific combinatio…
42 … (for example encrypt/decrypt, sign/verify), there is no requirement to include only one direction.
44 [Limitation.size] There is no requirement to include only support for certain key sizes.
46 …, for example single-part and multi-part, there is no mechanism to select only one or a subset of …
92 …upport for `psa_export_public_key` on the private key: there is no way to only include private-key…
94 …her than rely on them being implicitly enabled by the implementation. The only thing that is docum…
98 For elliptic curve key types, only the specified curves are included. To include a curve, include a…
[all …]
|
| D | psa-driver-interface.md | 25 * **Opaque** drivers implement cryptographic operations on keys that can only be used inside a prot…
37 …ple C function calls. Interactions with platform-specific hardware happen only inside the driver (…
94 … driver. If specified, the core will invoke this capability of the driver only when performing one…
95 …ations). If specified, the core will invoke this capability of the driver only when performing one…
96 …ations). If specified, the core will invoke this capability of the driver only for operations invo…
97 …tegers). If specified, the core will invoke this capability of the driver only for operations invo…
211 …meter of type `size_t` that indicates the buffer size. In-out buffers are only used when the input…
215 Input buffers and other input-only parameters (`const` pointers) may be in read-only memory. Overla…
221 * `"hash_compute"` (transparent drivers only): calculation of a hash. Called by `psa_hash_compute()…
254 This family applies to transparent drivers only.
[all …]
|
| /mbedtls-3.6.0/scripts/ |
| D | code_style.py | 45 # this script only depends on Git, Python and uncrustify, and not other
58 The optional argument since is a commit, indicating to only list files
62 Only C files are included, and certain files (generated, or 3rdparty)
73 cmd = ["git", "log", since + "..HEAD", "--name-only", "--pretty=", "--"] + src_files
77 cmd = ["git", "diff", "--name-only", "--"] + src_files
177 print("Note: The only supported version is " +
185 help=('only check files modified since the specified commit'
188 # --subset is almost useless: it only matters if there are no files
194 help='only check the specified files (default with non-option arguments)')
201 # We only check files that are known to git
|
| /mbedtls-3.6.0/tests/scripts/ |
| D | all.sh | 220 # only does word splitting.
235 By default, run all tests. With one or more COMPONENT, run only those.
250 -q|--quiet Only output component names, and errors if any.
268 instead of running only those.
514 # only does word splitting.
752 # only doing builds). Not all tests run OpenSSL and GnuTLS, but this
802 # past this point, no call to check_tool, only printing output
848 # 2c. Adjust MBEDTLS_ symbols in mbedtls_config.h. This only affects the
856 # calling scripts/config.py on this file remains the only option.
1195 # We can only compile, not link, since our test and sample programs
[all …]
|
| D | set_psa_test_dependencies.py | 17 # Only features that affect what can be done are listed here.
49 # Only modules that provide cryptographic mechanisms are listed here.
95 'PSA_ALG_AEAD_WITH_SHORTENED_TAG', # only a modifier
96 'PSA_ALG_ANY_HASH', # only meaningful in policies
97 'PSA_ALG_KEY_AGREEMENT', # only a way to combine algorithms
98 'PSA_ALG_TRUNCATED_MAC', # only a modifier
102 'PSA_ALG_AT_LEAST_THIS_LENGTH_MAC', #only a modifier
103 'PSA_ALG_AEAD_WITH_AT_LEAST_THIS_LENGTH_TAG', #only a modifier
143 # Storage format tests that only look at how the file is structured and
|
| /mbedtls-3.6.0/docs/architecture/psa-migration/ |
| D | psa-limitations.md | 8 subtle-but-important issues have been missed. The only way to be really sure
44 Currently, the PSA Crypto API can only perform FFDH with a limited set of
52 7919 which allows use of named groups in TLS 1.2 - however as this is only an
56 In TLS 1.3 the situation will be simpler: named groups are the only
69 would still be available in TLS 1.3, just not in 1.2.) (Can only be done in
71 3. Variant of the precedent: only drop client-side support. Server-side is
74 APIs and tell people to use `mbedtls_ssl_conf_groups()` instead. (Can only be
76 4. Implement RFC 7919, support DHE-RSA and DHE-PSK only in conjunction with it
78 client-side the only option is to offer named groups and break the handshake
83 time; making it mandatory can only be done in 4.0 or another major version.)
[all …]
|
| D | strategy.md | 74 Currently this option controls not only the presence of restartable APIs in
77 TLS and X.509 layers can't both use only PSA APIs and get restartable
130 above, and is only potentially relevant for G4.)
182 - Upside: changes mostly contained in one place, TLS/X.509 code only needs to
194 function also allows for key isolation (the key is only held by PSA,
196 still stored outside of PSA most of the time, supporting only G1).
206 code, and a contained change in TLS code. (It only supported a subset of
244 Criterion (c) ensures not only test coverage, but that driver-based builds are
277 - Step 0 is achieved for most algorithms, with only a few gaps remaining.
279 `MBEDTLS_USE_PSA_CRYPTO` is enabled with only a few gaps remaining (see
[all …]
|
| D | md-cipher-dispatch.md | 75 …es may change without notice.” In practice, this may mean constraints not only on how to write dri…
88 …d of legacy APIs for cryptographic calculations. `MBEDTLS_USE_PSA_CRYPTO` only applies to `pk.h`, …
92 * Make non-covered modules call PSA, but only [when this will actually work](#why-psa-is-not-always…
146 …ntation: calling a PSA accelerator would be a behavior change, acceptable only if this does not ad…
202 …only `PSA_WANT_ALG_SHA_256` and not `MBEDTLS_SHA256_C` is enabled (which implies that PSA's SHA-25…
208 …only the server has access to an accelerator so it's best to call the server, and plausible use ca…
211 …ation. In this case, we would prefer PSA for the acceleration, but we can only do this if the acce…
213 …ls to indicate that the algorithm is available through the legacy domain, only through the PSA dom…
233 … Legacy support is automatically enabled if PSA support is requested, but only if there is no acce…
237 …only save at best a very small amount of code size in the PSA dispatch code. This may be more desi…
[all …]
|
| /mbedtls-3.6.0/include/mbedtls/ |
| D | lms.h | 6 * This implementation currently only supports a single parameter set
30 /* Currently only defined for SHA256, 32 is the max hash output size */
49 /* The length of a hash output, Currently only implemented for SHA256.
73 * We are only implementing a subset of the types, particularly H10, for the sake of simplicity.
81 * We are only implementing a subset of the types, particularly N32_W8, for the sake of simplicity.
100 per IANA. Only SHA256_N32_W8 is
125 Boolean values only. */
151 Boolean values only. */
165 per IANA. Only SHA256_N32_W8 is
168 IANA. Only SHA256_M32_H10 is currently
[all …]
|
| D | pkcs7.h | 16 * - The RFC specifies 6 different content types. The only type currently
18 * - The only supported PKCS #7 Signed Data syntax version is version 1
20 * DER only.
22 * in the Signed Data type. Only one digest algorithm is supported in Mbed TLS.
24 * certificates. In Mbed TLS, this list can only contain 0 or 1 certificates
137 * Structure holding PKCS #7 structure, only signed data for now
156 * \param buf The buffer holding only the DER encoded PKCS #7 content.
|
| D | debug.h | 160 * library only.
179 * library only.
200 * library only.
221 * library only.
243 * library only.
264 * library only.
272 only works for the built-in implementation. */
295 * library only.
|
| D | mbedtls_config.h | 117 * The time does not need to be correct, only time differences are used,
313 * This only works with GCC and Clang. With other compilers, you may want to
348 * Only works if you have MBEDTLS_TIMING_C enabled.
363 * This replaces the whole module. If you only want to replace one of the
406 * macros as described above. The only difference is that you have to make sure
418 * This replaces only one function. The header file from Mbed TLS is still
442 * alternative implementations should use the RNG only for generating
588 * Use only 128-bit keys in AES operations to save ROM.
609 * If only one implementation is present, runtime detection will not be used.
632 * This is only supported on platforms where #MBEDTLS_CHECK_RETURN is
[all …]
|
| /mbedtls-3.6.0/docs/architecture/ |
| D | psa-thread-safety.md | 12 In particular, if you either protect all PSA calls with a mutex, or only ever call PSA functions fr…
14 …ld be ok to add new platform requirements if they're only needed for PSA drivers, or if they're on…
58 * By default, each driver only has at most one entry point active at any given time. In other words…
97 …tls_psa_crypto_configure_entropy_sources` (only if `MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG` is enabled): …
102 …o_configure_entropy_sources` [`rng_state`] (only if `MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG` is enabled):…
189 …e the [“key slot state”](#key-slot-state), the contents of a key slot are only accessed as follows:
253 …hat no other thread can modify the slot content, and the accessing thread is only reading the slot.
262 * WRITING: a thread has exclusive access to the slot. This can only happen in specific circumstance…
268 * `psa_get_and_lock_key_slot_in_memory`: UNUSED or READING → READING. This function only accepts sl…
276 There is currently no indication of when a slot is in the WRITING state. This only happens between …
|
| /mbedtls-3.6.0/docs/architecture/testing/ |
| D | invasive-testing.md | 55 If the most practical way to test something is to add code to the product that is only useful for t…
57 * **Only use test-specific code when necessary.** Anything that can be tested through the documente…
88 …ry platform. Skipping tests on certain platforms may hide errors that are only apparent on such pl…
89 * Maintainability: tests should only enforce the documented behavior of the product, to avoid extra…
102 * Files in storage (PSA API only — in the Mbed TLS API, black-box unit tests are sufficient).
103 * Key slots (PSA API only).
105 * Communication handles (PSA crypto service only).
121 * Deleting files in storage (PSA API only).
145 …only add public interfaces if they are also useful in production, at least sometimes. For example,…
180 This approach is mostly portable since it only relies on C interfaces. A limitation is that the tes…
[all …]
|
| D | psa-storage-format-testing.md | 7 The goal of this document is to define a test strategy for the key store that not only validates th…
37 …e there would be no indication that more test cases used to exist. It can only be enforced through…
39 …s (which should only be done by retiring a version of the storage format), then we should keep the…
100 Some types only have one plausible representation. Others admit alternative plausible representatio…
121 Only relevant for secure element support. Not yet fully implemented.
|
| /mbedtls-3.6.0/ |
| D | SECURITY.md | 18 Only the maintained branches, as listed in [`BRANCHES.md`](BRANCHES.md),
60 limited. We are only aiming to provide protection against **publicly
129 - Turn on hardware acceleration for AES. This is supported only on selected
130 architectures and currently only available for AES. See configuration options
141 The HACL* implementation of X25519 taken from the Everest project only protects
145 The Everest variant is only used when `MBEDTLS_ECDH_VARIANT_EVEREST_ENABLED`
|
| /mbedtls-3.6.0/3rdparty/p256-m/p256-m/ |
| D | README.md | 2 only a subset of p256-m's files are present in Mbed TLS, this README may refer
39 - The API is minimal: only 4 public functions.
49 - Two test suites are provided: one for closed-box testing (using only the
54 rigged RNG; the last branch could only be reached by computing a discrete log
93 integer division, and for multiplication by default it only uses 16x16->32 bit
102 1. attackers who can only manipulate the input and observe the output;
151 p256-m doesn't use any dynamic memory (on the heap), only the stack. Here's
197 implementation of ECDH and ECDSA on P-256 only, that also targets constrained
216 TinyCrypto also uses no heap, only the stack. Here's the RAM used by each
307 platforms used for benchmarking, while TinyCrypt uses only C (and the
[all …]
|
