Home
last modified time | relevance | path

Searched full:only (Results 1 – 25 of 358) sorted by relevance

12345678910>>...15

/mbedtls-latest/tests/scripts/
Dcomponents-configuration-tls.sh26 msg "build: default with only stream cipher"
46 msg "test: default with only stream cipher"
53 msg "build: default with only stream cipher use psa"
74 msg "test: default with only stream cipher use psa"
81 msg "build: default with only CBC-legacy cipher"
101 msg "test: default with only CBC-legacy cipher"
104 msg "test: default with only CBC-legacy cipher - ssl-opt.sh (subset)"
109 msg "build: default with only CBC-legacy cipher use psa"
130 msg "test: default with only CBC-legacy cipher use psa"
133 msg "test: default with only CBC-legacy cipher use psa - ssl-opt.sh (subset)"
[all …]
Dset_psa_test_dependencies.py17 # 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-latest/tests/suites/
Dtest_suite_md.psa.data5 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 …]
Dtest_suite_block_cipher.psa.data1 AES - legacy only
5 AES - driver only
13 ARIA - legacy only
17 ARIA - driver only
25 Camellia - legacy only
29 Camellia - driver only
Dtest_suite_bignum_core.generated.data9356 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-latest/docs/
Ddriver-only-builds.md2 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
31 In addition, for each mechanism you want provided only by your driver:
42 For example, if you want SHA-256 to be provided only by a driver, you'll want
48 driver-only mechanisms. Note that this is already a requirement for any use of
56 For now, only the following (families of) mechanisms are supported:
62 (for now, only crypto, no X.509 or TLS support).
73 Supported means that when those are provided only by drivers, everything
82 It is possible to have all hash operations provided only by a driver.
98 a hash algorithm that is provided only by a driver, as mentioned in [General
[all …]
D3.0-migration-guide.md60 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-latest/library/
Daesni.h6 * \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
41 /* For 32-bit, we only support intrinsics */
57 * (Only implemented with gas syntax, only for 64-bit.)
73 * \note This function is only for internal use by other library
90 * \note This function is only for internal use by other library
108 * \note This function is only for internal use by other library
127 * \note This function is only for internal use by other library
[all …]
Ddebug_internal.h28 * library only.
47 * library only.
68 * library only.
89 * library only.
111 * library only.
132 * library only.
140 only works for the built-in implementation. */
163 * library only.
/mbedtls-latest/docs/proposed/
Dpsa-conditional-inclusion-c.md12 … 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 …]
Dpsa-driver-interface.md25 * **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-latest/docs/architecture/psa-migration/
Dmd-cipher-dispatch.md75 …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…
115 Hashes and HMAC (after the work on driver-only hashes):
129 Symmetric ciphers and AEADs (before work on driver-only cipher):
132 * AES, DES or 3DES in CBC mode without padding, decrypt only (!).
137 * In practice: 2DES or 3DES in CBC mode with PKCS7 padding, decrypt only
153 * AES in ECB mode, encrypt only.
158 * AES, Camellia or Aria in ECB mode, encrypt only.
164 * AES or DES in ECB mode, encrypt only.
[all …]
Dpsa-limitations.md8 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 …]
Dstrategy.md74 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 …]
Dpsa-legacy-bridges.md39 * Only PSA fully supports PSA accelerators and secure element integration.
40 * Only PSA supports isolating cryptographic material in a secure service.
92 Hashes do not involve keys, and involves no nontrivial data format. Therefore the only gap is with …
94 …s, key derivation, etc.). Therefore metadata about hashes is relevant not only when calculating ha…
96 …_psa_alg_from_type`, `mbedtls_md_type_from_psa_alg`) but they are declared only in private headers.
118 The legacy API only has generic support for two key types: RSA and ECC, via the pk module. ECC keys…
125 ECC keys are also involved in EC-JPAKE, but this happens internally: the EC-JPAKE interface only ne…
137 …PSA only supports predefined groups, whereas legacy only supports ad hoc groups. An existing appli…
170 * It is only available under `MBEDTLS_USE_PSA_CRYPTO`. This is not a priority concern, since we gen…
177 Gap: a way to copy a PSA key into a PK context. This can only be expected to work if the PSA key is…
[all …]
/mbedtls-latest/scripts/
Dcode_style.py45 # this script only depends on Git, Python and uncrustify, and not other
65 The optional argument since is a commit, indicating to only list files
69 Only C files are included, and certain files (generated, or 3rdparty)
102 "--name-only", "--pretty=", "--"] + src_files
107 "--name-only", "--pretty=", "--"] + framework_src_files
114 cmd = ["git", "diff", "--name-only", "--"] + src_files
118 cmd = ["git", "-C", "framework", "diff", "--name-only", "--"] + \
224 print("Note: The only supported version is " +
232 help=('only check files modified since the specified commit'
235 # --subset is almost useless: it only matters if there are no files
[all …]
/mbedtls-latest/include/mbedtls/
Dlms.h6 * 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 …]
Dssl.h92 * This error code can be returned only on server side if and only if early
149 /** Internal-only message signaling that further message-processing should be done */
153 /** Internal-only message signaling that a message arrived early. */
299 #define MBEDTLS_SSL_VERIFY_UNSET 3 /* Used only for sni_authmode */
390 * communicate with you anymore. Only change this value if you control
607 #define MBEDTLS_TLS_EXT_RECORD_SIZE_LIMIT 28 /* RFC 8449 (implemented for TLS 1.3 only) */
654 /* Dummy type used only for its size */
738 * Early data status, client side only.
841 * \note Only one timer at a time must be running. Calling this
857 * 1 if only the intermediate delay has passed,
[all …]
Dmbedtls_config.h117 * 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 …]
Dpkcs7.h16 * - 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
136 * Structure holding PKCS #7 structure, only signed data for now
155 * \param buf The buffer holding only the DER encoded PKCS #7 content.
/mbedtls-latest/docs/architecture/testing/
Dinvasive-testing.md55 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 …]
/mbedtls-latest/docs/architecture/psa-thread-safety/
Dpsa-thread-safety.md5 ….psa_crypto_init) thread-safe has been implemented. Implementations which only ever call PSA funct…
37 …me sequential ordering. We implement a weaker notion of thread-safety, we only guarantee thread-sa…
49 When only considering key management functions: Mbed TLS 3.6 abides by the minimum expectation for …
53 … be added to the PSA 1.2 specification, Mbed TLS 3.6 abides by these when only considering [key ma…
78 Code which was working prior to Mbed TLS 3.6 will still work. Implementations which only ever call …
82 Currently, the only threading library with support shipped in the code base is pthread (enabled by …
107 … thread-safe (`mbedtls_psa_random_init` and `mbedtls_psa_random_seed` are only thread-safe when ca…
119 …ds attempt to load the same persistent key, with the same key identifier, only one thread can succ…
123 If a mutex operation fails, which only happens if the mutex implementation fails, the error code `P…
129 `mbedtls_psa_crypto_free` must only be called by a single thread once all threads have completed th…
[all …]
/mbedtls-latest/3rdparty/p256-m/p256-m/
DREADME.md2 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 …]
/mbedtls-latest/
DChangeLog24 * In a PSA-client-only build (i.e. MBEDTLS_PSA_CRYPTO_CLIENT &&
71 The cryptographic mechanisms remain present, but they will only be
91 not cause the PSA subsystem to use HMAC_DRBG: it uses HMAC_DRBG only when
107 authentication anyway. Only TLS 1.3 servers were affected, and only with
146 * Fix server mode only build when MBEDTLS_SSL_SRV_C is enabled but
205 * psa_import_key() now only accepts RSA keys in the PSA standard formats.
253 implementation is able to take advantage of a driver that only
255 docs/driver-only-builds.md for full details and current limitations.
264 fully provided by drivers. See docs/driver-only-builds.md for full
352 be only partially supported (#3266).
[all …]
DSECURITY.md18 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`

12345678910>>...15