| /mbedtls-3.4.0/library/ |
| D | pkcs5.c | 217 unsigned char work[MBEDTLS_MD_MAX_SIZE]; in pkcs5_pbkdf2_hmac() local
243 if( ( ret = mbedtls_md_hmac_finish( ctx, work ) ) != 0 ) in pkcs5_pbkdf2_hmac()
249 memcpy( md1, work, md_size ); in pkcs5_pbkdf2_hmac()
267 work[j] ^= md1[j]; in pkcs5_pbkdf2_hmac()
271 memcpy( out_p, work, use_len ); in pkcs5_pbkdf2_hmac()
283 mbedtls_platform_zeroize( work, MBEDTLS_MD_MAX_SIZE ); in pkcs5_pbkdf2_hmac()
330 unsigned char work[PSA_HASH_MAX_SIZE]; in mbedtls_pkcs5_pbkdf2_hmac_ext()
378 if( ( status = psa_mac_sign_finish( &operation, work, out_size, &out_len ) ) in mbedtls_pkcs5_pbkdf2_hmac_ext()
382 memcpy( md1, work, out_len ); in mbedtls_pkcs5_pbkdf2_hmac_ext()
400 work[j] ^= md1[j]; in mbedtls_pkcs5_pbkdf2_hmac_ext()
[all …]
|
| /mbedtls-3.4.0/tests/git-scripts/ |
| D | README.md | 7 …hooks` to `<Mbed TLS root>/tests/git-scripts`, in order to make the hook scripts successfully work.
14 **Note: Currently the Mbed TLS git hooks work only on a GNU platform. If using a non-GNU platform, …
|
| /mbedtls-3.4.0/ |
| D | LICENSE | 36 "Work" shall mean the work of authorship, whether in Source or
38 copyright notice that is included in or attached to the work
41 "Derivative Works" shall mean any work, whether in Source or Object
44 represent, as a whole, an original work of authorship. For the purposes
49 "Contribution" shall mean any work of authorship, including
162 work stoppage, computer failure or malfunction, or any and all
179 APPENDIX: How to apply the Apache License to your work.
181 To apply the Apache License to your work, attach the following
|
| D | dco.txt | 21 (b) The contribution is based upon previous work that, to the best
24 work with modifications, whether created in whole or in part
|
| D | README.md | 50 …, IAR 8 and Visual Studio 2013. More recent versions should work. Slightly older versions may work.
55 * Doxygen 1.8.11 or later (if building the documentation; slightly older versions should work).
157 CC=your_cc` will *not* work (similarly with `CFLAGS` and other variables).
|
| D | CONTRIBUTING.md | 27 1. Send a pull request (PR) and work with us until it gets merged and published. Contributions may …
33 …ould not be necessary for a user to make any changes to their own code to work with a newer versio…
|
| D | BRANCHES.md | 32 number, and your code will still build, be secure, and work.
|
| D | CMakeLists.txt | 30 # Setting the CMP0012 policy to NEW is required for FindPython3 to work with CMake 3.18.2
|
| /mbedtls-3.4.0/docs/proposed/ |
| D | psa-driver-integration-guide.md | 4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.**
8 … Mbed TLS yet and is disabled by default. You can enable the experimental work in progress by sett…
|
| D | psa-driver-developer-guide.md | 4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.**
10 … Mbed TLS yet and is disabled by default. You can enable the experimental work in progress by sett…
|
| D | psa-driver-wrappers-codegen-migration-guide.md | 4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.**
|
| D | psa-conditional-inclusion-c.md | 24 …DTLS_xxx_ALT` symbols are somewhat inconsistent, and in particular do not work well for asymmetric…
30 …ed Mbed TLS build must not include it. The granularity of mechanisms must work for typical use cas…
216 …rent designs. Is there serious potential for confusion? Do we understand how the combinations work?
|
| /mbedtls-3.4.0/3rdparty/everest/ |
| D | README.md | 5 …ms are supported, although the version in `everest/library/legacy` should work on most systems. Th…
|
| /mbedtls-3.4.0/docs/architecture/testing/ |
| D | invasive-testing.md | 20 …s what the crypto/keystore and X.509 parts of the library are about. More work is needed to fully …
88 * Portability: tests should work on every platform. Skipping tests on certain platforms may hide er…
89 …hould only enforce the documented behavior of the product, to avoid extra work when the product's …
180 …thing we currently do). Another limitation is that this approach does not work for users who patch…
189 | | ~ Doesn't work if the users rewrite an internal module |
197 * This does not work for platform-dependent properties unless we have a formal model of the platfor…
218 | | ~ Doesn't work if the users rewrite an internal module |
296 …in the PSA key store code, in particular that `psa_close_key` and `psa_destroy_key` work correctly.
|
| D | psa-storage-format-testing.md | 5 … is possible to create a persistent key and read it back later. This must work even if Mbed TLS ha…
9 …entations are not intended to have compatible storage formats. Downgrading is not required to work.
|
| /mbedtls-3.4.0/docs/architecture/psa-migration/ |
| D | strategy.md | 77 It will then require follow-up work to make use of the new PSA API in
83 TLS, X.509 or PK. We can try to work around that by calling (the relevant
89 auto-enable the latter, as it won't build or work out of the box on all
90 platforms. There are two kinds of things we'd need to do if we want to work
238 We can roughly divide the work needed to get there in the following steps:
260 work is divided into PRs, sometimes not. For example, in situations where it's
300 application code keeps working unchanged. An work-in-progress example of
380 we're making some part of the library work with hashes provided only by
423 Unfortunately that's unlikely to fully work. For example, the MD layer uses the
|
| D | psa-limitations.md | 9 is, of course, to actually do the migration work.
70 when moving to PSA. Server-side would work as above; unfortunately
74 the one that requires the most work, but it would deliver value beyond PSA
|
| D | testing.md | 43 (`mbedtls_pk_get_type()` etc.) work and the functions that are expected to
|
| /mbedtls-3.4.0/docs/architecture/ |
| D | alternative-implementations.md | 22 …ot currently support alternative implementations. If this module does not work on your platform, d…
54 …anagement that can move objects on the heap.) That is, call sequences like the following must work:
|
| /mbedtls-3.4.0/scripts/data_files/ |
| D | query_config.fmt | 96 * WARNING: This does not work for expanding function-like macros. However,
|
| /mbedtls-3.4.0/tests/suites/ |
| D | test_suite_psa_crypto_persistent_key.function | 27 * upgrades work smoothly, so it's a stable interface nonetheless.
|
| D | test_suite_entropy.function | 142 /* Double free is not explicitly documented to work, but it is convenient
|
| D | test_suite_cipher.function | 109 * guaranteed to work with new ciphers or with alternative implementations of
110 * individual ciphers, and it doesn't work with the PSA wrappers. So don't do
|
| D | test_suite_bignum_core.function | 565 /* We only need to work with X4 or X8, depending on sizeof(mbedtls_mpi_uint) */
665 /* We only need to work with X4 or X8, and cy4 or cy8, depending on sizeof(mbedtls_mpi_uint) */
|
| D | host_test.function | 544 * structures, which should work on every modern platform. Let's be sure.
|
