| /mbedtls-3.7.0/tests/suites/ |
| D | test_suite_alignment.data | 52 Byteswap 16 all-zero
55 Byteswap 16 all-ones
64 Byteswap 32 all-zero
67 Byteswap 32 all-ones
73 Byteswap 64 all-zero
76 Byteswap 64 all-ones
|
| D | test_suite_base64.data | 1 enc_char (all digits)
4 dec_value (all characters)
162 Base64 encode hex all valid input bytes #0
165 Base64 encode hex all valid input bytes #1
168 Base64 encode hex all valid input bytes #2
171 Base64 encode all valid output characters at all offsets
189 Base64 decode all valid input characters at all offsets
|
| /mbedtls-3.7.0/docs/ |
| D | driver-only-builds.md | 70 For each family listed above, all the mentioned alorithms/key types are also
71 all the mechanisms that exist in PSA API.
82 It is possible to have all hash operations provided only by a driver.
88 - and similarly for all supported hash algorithms: `MD5`, `RIPEMD160`,
92 In such a build, all crypto operations (via the PSA Crypto API, or non-PSA
144 - you have driver support for all ECC curves that are enabled (that is, for
161 - you have driver support for all enabled ECC key pair operations - that is,
179 In such builds, all crypto operations via the PSA Crypto API will work as
240 In order for a build to be driver-only (no built-in implementation), all the
249 algorithms will be disabled, provided all the requested curves and key types
[all …]
|
| D | use-psa-crypto.md | 83 context: `mbedtls_pk_check_pair()`, `mbedtls_pk_debug()`, all public key
150 Other than the above exceptions, all crypto operations are based on PSA when
160 Other than the above exception, all crypto operations are based on PSA when
172 Other than the above exceptions, all crypto operations are based on PSA when
|
| /mbedtls-3.7.0/scripts/mbedtls_dev/ |
| D | build_tree.py | 14 return all(os.path.isdir(os.path.join(path, subdir))
19 return all(os.path.isdir(os.path.join(path, subdir))
61 if not all(os.path.isdir(d) for d in ["include", "library", "tests"]):
|
| /mbedtls-3.7.0/docs/architecture/ |
| D | Makefile | 3 default: all
9 all: html pdf target
|
| D | tls13-support.md | 30 all of them:
62 Potentially all ECDHE groups:
65 Potentially all DHE groups:
88 The TLS 1.3 implementation is compatible with nearly all TLS 1.2
345 functions of that implementation. They are implemented as a switch over all the
351 The implementation does not go systematically through all states as this would
370 care about the MBEDTLS_ERR_SSL_WANT_WRITE error code. Furthermore, all pending
|
| /mbedtls-3.7.0/docs/proposed/ |
| D | Makefile | 3 default: all
14 all: html pdf target
|
| /mbedtls-3.7.0/docs/architecture/psa-migration/ |
| D | psa-limitations.md | 2 1.1) that may impact our ability to (1) use it for all crypto operations in
3 TLS and X.509 and (2) support isolation of all long-term secrets in TLS (that
58 coincidentally, all the groups used by RFC 7919 and TLS 1.3 are included
157 presents, all values must match except possibly for the salt length, where the
174 `mbedtls_pk_verify_ext()` uses encoding hash = mgf1 hash, it looks like all
195 - all three hashes are equal
256 all using saltlen = keylen - hashlen - 2, except for server9-defaults which is
287 all using saltlen = keylen - hashlen - 2.
313 all using saltlen = keylen - hashlen - 2.
320 1. Doing all verifications with `PSA_ALG_RSA_PSS_ANY_SALT` - while this
[all …]
|
| D | strategy.md | 15 As of Mbed TLS 3.2, most of (G1) and all of (G2) is implemented when
55 out of the box on all platforms, and even less
84 PK/X.509/TLS in all places where we currently allow restartable operations.
95 auto-enable the latter, as it won't build or work out of the box on all
146 This strategy is currently (early 2023) used for all operations in the PK
240 b. with all tests passing,
251 dispatch to PSA, but not the low-level legacy API, for all operations.
263 Note: the fact that step 1 is not achieved for all of libmbedcrypto (see
283 - Step 1 is not achieved for all of the crypto library when it come to
297 ECJPAKE), however they all depend on `ECP_C` which in turn depends on
[all …]
|
| /mbedtls-3.7.0/programs/fuzz/ |
| D | Makefile | 22 .PHONY: all check test clean
24 all: $(BINARIES) target
|
| /mbedtls-3.7.0/ |
| D | .gitignore | 12 # CMake generates *.dir/ folders for in-tree builds (used by MSVC projects), ignore all of those:
45 # CMake generates *.dir/ folders for in-tree builds (used by MSVC projects), ignore all of those:
|
| D | LICENSE | 23 "Legal Entity" shall mean the union of the acting entity and all
109 that You distribute, all copyright, patent, trademark, and
169 work stoppage, computer failure or malfunction, or any and all
228 software--to make sure the software is free for all its users. This
248 gratis or for a fee, you must give the recipients all the rights that
268 patent must be licensed for everyone's free use or not licensed at all.
296 copyright notice and disclaimer of warranty; keep intact all the
307 above, provided that you also meet all of these conditions:
314 part thereof, to be licensed as a whole at no charge to all third
371 code means all the source code for all modules it contains, plus any
[all …]
|
| D | README.md | 41 …hose systems are always complete and up-to-date. The others should reflect all changes present in …
81 * Run `make generated_files` to generate all the configuration-independent files.
82 * On Unix/POSIX systems, run `tests/scripts/check-generated-files.sh -u` to generate all the config…
83 * On Windows, run `scripts\make_generated_files.bat` to generate all the configuration-independent …
150 - `Check`. This activates the compiler warnings that depend on optimization and treats all warnin…
230 The solution file `mbedTLS.sln` contains all the basic projects needed to build the library and all…
251 - `tests/scripts/all.sh` runs a combination of the above tests, plus some more, with various buil…
253 Instead of manually installing the required versions of all tools required for testing, it is possi…
296 …t aim to implement the whole specification; in particular it does not implement all the algorithms.
309 …he code of the corresponding software implementation. This is not yet supported for all mechanisms.
|
| D | .gitattributes | 1 # Classify all '.function' files as C for syntax highlighting purposes
|
| D | Makefile | 7 .PHONY: all no_test programs lib tests install uninstall clean test check lcov apidoc apidoc_clean
9 all: programs tests target
|
| /mbedtls-3.7.0/scripts/data_files/driver_templates/ |
| D | psa_crypto_driver_wrappers.h.jinja | 100 /* Unregister all secure element drivers, so that we restart from
131 * cycle through all known transparent accelerators */
205 * cycle through all known transparent accelerators */
292 * cycle through all known transparent accelerators */
396 * cycle through all known transparent accelerators */
526 * cycle through all known transparent accelerators */
618 * cycle through all known transparent accelerators */
786 /* Cycle through all known transparent accelerators */
893 * cycle through all known transparent accelerators */
1053 * cycle through all known transparent accelerators */
[all …]
|
| /mbedtls-3.7.0/3rdparty/p256-m/p256-m/ |
| D | README.md | 41 - The API uses arrays of octets for all input and output.
52 - The resulting branch coverage is maximal: closed-box testing reaches all
71 and indeed all Short Weierstrass curves, have a number of pitfalls including
284 - While p256-m fully validates all inputs, Tinycrypt's ECDH shared secret
368 Not all formulas associated with affine or Jacobian coordinates are complete;
379 for ECDSA verify where all data is public);
399 This layer builds on the others, but unlike them, all inputs and outputs are
468 For multiple other curves, define all the constants, and from this layer's API
481 add a "curve id" parameter to all functions in this layer.
488 the point 0. As far as I know, all Short Weierstrass curves standardized so
[all …]
|
| /mbedtls-3.7.0/tests/git-scripts/ |
| D | pre-push.sh | 34 tests/scripts/all.sh -q -k 'check_*'
|
| /mbedtls-3.7.0/tests/scripts/ |
| D | all-in-docker.sh | 25 run_in_docker tests/scripts/all.sh \
|
| D | check-generated-files.sh | 15 This script checks that all generated file are up-to-date. If some aren't, by
|
| D | basic-in-docker.sh | 25 run_in_docker tests/scripts/all.sh 'check_*'
|
| /mbedtls-3.7.0/library/ |
| D | Makefile | 210 .PHONY: all static shared clean
213 all: static target
215 all: shared static target
|
| /mbedtls-3.7.0/docs/architecture/testing/ |
| D | driver-interface-test-strategy.md | 41 … API functions involve multiple driver methods; these should validate that all the expected driver…
45 …heck that the expected driver is called. This does not need to be done for all operations (use a w…
48 …le a driver that provides the MAC methods must provide all or none). In those cases, test with all…
112 * Implementing all the methods.
|
| D | invasive-testing.md | 143 …all the features we want to test in the public interface. Then the tests can be truly black-box. T…
145 … For example, the main purpose of `mbedtls_psa_crypto_free` is to clean up all resources in tests,…
160 …all the features we want to test in undocumented interfaces. Undocumented interfaces are described…
264 | Portability | !! Not all environments have a debugger, and even if they do, we'd need completely …
292 Solution: TODO. We don't test this at all at this point.
300 …ts that call `mbedtls_psa_crypto_free` with keys still open, to verify that it does close all keys.
358 … that can fail. This is the only failure point for `psa_crypto_init` that is present in all builds.
|
