/mbedtls-development/ |
A D | LICENSE | 31 "Object" form shall mean any form resulting from mechanical 49 "Contribution" shall mean any work of authorship, including 83 institute patent litigation against any entity (including a 86 or contributory patent infringement, then any patent licenses 95 (a) You must give any other recipients of the Work or 104 excluding those notices that do not pertain to any part of 127 for any such Derivative Works as a whole, provided Your use, 134 this License, without any additional terms or conditions. 172 of any other Contributor, and only if You agree to indemnify, 173 defend, and hold each Contributor harmless for any liability [all …]
|
A D | BRANCHES.md | 3 At any point in time, we have a number of maintained branches consisting of: 29 modification with any later release x.y'.z' with the same major version 57 re-compiling) and to avoid any increase in code size or RAM usage, or in the
|
A D | CONTRIBUTING.md | 5 …- As with any open source project, contributions will be reviewed by the project team and communit… 28 … versions of the library and it should not be necessary for a user to make any changes to their ow…
|
A D | README.md | 69 * If not cross-compiling, running `make` with any target, or just `make`, will automatically genera… 133 - `Release`. This generates the default code without any unnecessary information in the binary fi… 259 …e communication. Second, it can also be used independently of other PSA components on any platform.
|
/mbedtls-development/ChangeLog.d/ |
A D | psa_alg_rsa_pss.txt | 5 PSA_ALG_RSA_PSS_ANY_SALT to accept any salt length. Fixes #4946.
|
/mbedtls-development/tests/suites/ |
A D | test_suite_random.data | 38 # with something larger than any RNG call made by Mbed TLS itself expects.
|
A D | helpers.function | 98 * If any slots are in use, mark the current test as failed.
|
A D | test_suite_psa_crypto_metadata.data | 209 Asymmetric signature: RSA PSS-any-salt SHA-256 245 Asymmetric signature: RSA PSS-any-salt with wildcard hash
|
A D | main_test.function | 127 * parameter array and do not perform any error detection.
|
A D | test_suite_psa_crypto.data | 3462 PSA signature size: RSA keypair, 1024 bits, PSS-any-salt 3482 PSA import/exercise RSA keypair, PSS-any-salt-SHA-256 3494 PSA import/exercise RSA public key, PSS-any-salt-SHA-256 3678 PSA verify hash: RSA-1024 PSS-any-salt SHA-256, slen=0 3686 PSA verify hash: RSA-1024 PSS-any-salt SHA-256, slen=31 3694 PSA verify hash: RSA-1024 PSS-any-salt SHA-256, slen=32 3702 PSA verify hash: RSA-1024 PSS-any-salt SHA-256, slen=94 3710 PSA verify hash: RSA-1024 PSS-any-salt SHA-512, slen=61 3718 PSA verify hash: RSA-1024 PSS-any-salt SHA-512, slen=62 3726 PSA verify hash: RSA-528 PSS-any-salt SHA-512, slen=0 [all …]
|
A D | test_suite_ssl.function | 635 * \retval MBEDTLS_TEST_ERROR_CONTEXT_ERROR, if any of the needed context 640 * This function will also return any error from 672 * \retval MBEDTLS_TEST_ERROR_CONTEXT_ERROR, if any of the needed context 676 * This function will also return any error other than 2334 /* The result depends on whether any data was sent */ 2473 /* The result depends on whether any data was sent */ 3630 * sure our padding checking code does not perform any out-of-bounds reads 4261 /* Allocate exact size so that asan/valgrind can detect any overwrite */ 4301 /* Allocate exact size so that asan/valgrind can detect any overread */ 4345 /* Without any modification, we should be able to successfully
|
/mbedtls-development/.github/ |
A D | pull_request_template.md | 21 If there is any API change, what's the incentive and logic for it.
|
/mbedtls-development/scripts/ |
A D | config.py | 78 def any(self, *names): member in Config 80 return any(self.__contains__(name) for name in names)
|
/mbedtls-development/docs/ |
A D | 3.0-migration-guide.md | 57 The change affects users who use any of the following functions: 79 treated differently from any other invalid pointer, and typically leads to a 108 doesn't have any entropy source, you should use `MBEDTLS_ENTROPY_NV_SEED` 131 Please use the new names directly in your code; `scripts/rename.pl` (from any 525 and it may change in incompatible ways at any time. 550 extension if it contains any unsupported certificate policies. 676 Please switch to any of the modern, recommended ciphersuites (based on 678 any, encourage them to upgrade their software. 685 Please switch to any of the modern, recommended ciphersuites (based on 687 any, encourage them to upgrade their software. [all …]
|
A D | getting_started.md | 62 To use the Mbed Crypto APIs, call `psa_crypto_init()` before calling any other API. This initialize… 363 …tup()` or `psa_cipher_decrypt_setup()`, you can terminate the operation at any time by calling `ps… 365 The call to `psa_cipher_abort()` frees any resources associated with the operation, except for the … 368 …ate_iv()`, `psa_cipher_set_iv()` or `psa_cipher_update()` fails (returning any status other than `… 373 You must call `psa_cipher_abort()` at some point for any operation that is initialized successfully… 489 … you can terminate the operation at any time by calling `psa_hash_abort()`. The call to `psa_hash_… 492 1. A call to `psa_hash_update()` fails (returning any status other than `PSA_SUCCESS`). 498 You must call `psa_hash_abort()` at some point for any operation that is initialized successfully (…
|
A D | use-psa-crypto.md | 19 Stability: any API that's only available when `MBEDTLS_USE_PSA_CRYPTO` is 20 defined is considered experimental and may change in incompatible ways at any
|
/mbedtls-development/docs/proposed/ |
A D | psa-driver-interface.md | 35 …any platform-specific consideration. Driver calls are simple C function calls. Interactions with p… 123 …nistic ECDSA signatures (but not signature verification) using any hash algorithm and any curve th… 237 …this fails, the core destroys the operation context object without calling any other driver entry … 239 …any entry point fails, the core calls the driver's `xxx_abort` entry point for this operation fami… 434 The init entry point does not take any parameter. 524 …l-entropy” means that the data is uniformly distributed and independent of any other observable qu… 588 …any value other than `PSA_ERROR_NOT_SUPPORTED` (`PSA_SUCCESS` or a different error code), this val… 684 3. The core saves the resulting wrapped key material and any other data that the key context may co… 774 The core guarantees that the size of the output buffer (`data_size`) is sufficient to export any ke… 971 The driver is allowed to update the state at any time. Is this ok? [all …]
|
A D | psa-conditional-inclusion-c.md | 71 … feature is available through the PSA API. These symbols should be used in any place that requires… 97 Rationale: Finite-field Diffie-Hellman code is usually not specialized for any particular group, so… 166 Since configuration symbols must be undefined or 1, any other value should trigger an `#error`. 194 …nism proposed here. The approximation considers a feature to be enabled if any part of it is enabl…
|
/mbedtls-development/docs/architecture/testing/ |
A D | driver-interface-test-strategy.md | 79 * Test that `psa_destroy_key()` does not leave any trace of the key. 83 …</sub>, ..., M<sub>n</sub>). If the operation is interrupted by a reset at any point, it must be e… 90 …done by e.g. using a key that is supposed to be present) and does not have any unexpected content …
|
A D | invasive-testing.md | 49 > # and not expected to be raised any time soon) is less than the maximum 69 …In such cases, the function should generally not modify its parameters, so any pointer argument sh… 280 …ecause the danger is that the compiler optimizes the zeroization away, and any C code that observe… 288 …f. Use the cleanup code (after the `exit` label in test functions) to free any memory that the fun…
|
/mbedtls-development/docs/architecture/ |
A D | psa-crypto-implementation-structure.md | 22 … in the PSA Cryptography API specification but does not perform on its own any cryptographic opera… 66 In case of any error occurring at step 3 or 4, psa_fail_key_creation() is called. It wipes and clea…
|
A D | mbed-crypto-storage-specification.md | 33 We do not make any promises regarding key storage, or regarding the nonvolatile random seed file on… 66 The file format is just the seed as a byte string with no metadata or encoding of any kind.
|
/mbedtls-development/programs/fuzz/ |
A D | README.md | 24 And you can run any of the fuzz targets like `fuzz_client`.
|
/mbedtls-development/doxygen/ |
A D | mbedtls.doxyfile | 187 # member inherits the documentation from any documented member that it 305 # member in the group (if any) for the other members of the group. By default 424 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 780 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) 811 # doxygen to hide any special comment blocks from generated source code 897 # for the proper inclusion of any scripts and style sheets that doxygen 1153 # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 1181 # to manually remove any form_*.png images from the HTML output directory 1189 # Note that when changing this option you need to delete any form_*.png files 1234 # and DHTML and should work on any modern browser. Note that when using
|
/mbedtls-development/tests/scripts/ |
A D | all.sh | 238 -q|--quiet Only output component names, and errors if any. 239 -f|--force Force the tests to overwrite any modified files. 251 files. Do not run any components unless they are 254 to any specified component. May be repeated.
|