| /mbedtls/library/ |
| A D | pkcs5.c | 277 unsigned char work[MBEDTLS_MD_MAX_SIZE]; in pkcs5_pbkdf2_hmac() local
306 if ((ret = mbedtls_md_hmac_finish(ctx, work)) != 0) { in pkcs5_pbkdf2_hmac()
314 memcpy(md1, work, md_size); in pkcs5_pbkdf2_hmac()
333 mbedtls_xor(work, work, md1, md_size); in pkcs5_pbkdf2_hmac()
337 memcpy(out_p, work, use_len); in pkcs5_pbkdf2_hmac()
351 mbedtls_platform_zeroize(work, MBEDTLS_MD_MAX_SIZE); in pkcs5_pbkdf2_hmac()
|
| /mbedtls/ |
| A D | LICENSE | 43 "Work" shall mean the work of authorship, whether in Source or
45 copyright notice that is included in or attached to the work
56 "Contribution" shall mean any work of authorship, including
186 APPENDIX: How to apply the Apache License to your work.
279 refers to any such program or work, and a "work based on the Program"
281 that is to say, a work containing the Program or a portion of it,
289 is covered only if its contents constitute a work based on the
305 of it, thus forming a work based on the Program, and copy and
328 These requirements apply to the modified work as a whole. If
369 The source code for a work means the preferred form of the work for
[all …]
|
| A 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
|
| A D | README.md | 50 …, IAR 8 and Visual Studio 2017. 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).
162 CC=your_cc` will *not* work (similarly with `CFLAGS` and other variables).
302 …ryptographic accelerators, secure elements and random generators. This is work in progress. Please…
|
| A 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…
|
| A D | BRANCHES.md | 38 number, and your code will still build, be secure, and work.
|
| /mbedtls/tests/git-scripts/ |
| A 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/docs/ |
| A D | driver-only-builds.md | 75 work in the same way as if the mechanisms where built-in, except as documented
93 APIs), as well as X.509 and TLS, will work as usual, except that direct calls
119 `MBEDTLS_MD_C` and still getting crypto operations, X.509 and TLS to work as
179 In such builds, all crypto operations via the PSA Crypto API will work as
293 `MBEDTLS_PKCS1_V21`, and RSA will still work in PSA Crypto.
298 PSA Crypto works. In particular, PK, X.509 and TLS will _not_ work with
376 - `MBEDTLS_CIPHER_C`: the `mbedtls_cipher_xxx()` APIs will only work with
380 - `MBEDTLS_PKCS5_C`: encryption/decryption (PBES2, PBE) will only work with
382 - PEM decryption will only work with ciphers that are built-in.
423 algorithm) in order to work with a driver.
[all …]
|
| A D | psa-driver-example-and-guide.md | 5 …work-in-progress driver system. The [PSA Driver Interface](https://github.com/Mbed-TLS/mbedtls/blo…
|
| /mbedtls/docs/architecture/psa-migration/ |
| A D | md-cipher-dispatch.md | 12 A difference between the original strategy and the current one is that in this work, we are not tre…
56 …this work is to arrange for more non-PSA interfaces to use PSA interfaces under the hood, without …
90 In this work, we want two things:
105 For the purposes of this work, three domains emerge:
115 Hashes and HMAC (after the work on driver-only hashes):
129 Symmetric ciphers and AEADs (before work on driver-only cipher):
207 …ve a fallback) if their caller is not in the PSA domain and the PSA call is not guaranteed to work.
235 Let us work through the example of RSA-PSS which calculates a hash, as in [see issue \#6497](https:…
298 * Mixed-domain code can assume that PSA buffer calculations work correctly for all algorithms that …
357 …xtend it to other block ciphers at the moment), while GCM and CCM need to work with 3 block cipher…
[all …]
|
| A D | strategy.md | 21 As of early 2023, work towards G5 is in progress: Mbed TLS 3.3 and 3.4 saw
83 It will then require follow-up work to make use of the new PSA APIs in
89 TLS, X.509 or PK. We can try to work around that by calling (the relevant
95 auto-enable the latter, as it won't build or work out of the box on all
96 platforms. There are two kinds of things we'd need to do if we want to work
247 We can roughly divide the work needed to get there in the following steps:
270 work is divided into PRs, sometimes not. For example, in situations where it's
349 we're making some part of the library work with hashes provided only by
393 Unfortunately that's unlikely to fully work. For example, the MD layer uses the
|
| A D | psa-limitations.md | 9 is, of course, to actually do the migration work.
77 when moving to PSA. Server-side would work as above; unfortunately
81 the one that requires the most work, but it would deliver value beyond PSA
|
| A D | testing.md | 43 (`mbedtls_pk_get_type()` etc.) work and the functions that are expected to
|
| A D | psa-legacy-bridges.md | 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…
241 * No further work is needed about RSA specifically. The amount of metadata other than hashes is suf…
242 * No further work is needed about ECC specifically. We have just added adequate functions.
243 * No further work is needed about DHM specifically. There is no good way to translate the relevant …
|
| /mbedtls/docs/architecture/psa-thread-safety/ |
| A D | psa-thread-safety.md | 7 Summary of recent work:
27 * The [Future work](#future-work) section outlines our long-term goals for thread-safety; it also a…
78 …work. Implementations which only ever call PSA functions from a single thread, or which protect al…
255 It is now possible for individual tests to spin up multiple threads. This work has made the global …
261 Our testing is a work in progress. It is not feasible to run our traditional, single-threaded, test…
273 Through future work on testing, it would be good to:
288 ## Future work
292 …m to make the entirety of the PSA API thread-safe. This will build on the work that we have alread…
316 …ion requirements](#long-term-key-destruction-requirements). Destruction would then work as follows:
335 ### Future driver work argument
[all …]
|
| /mbedtls/tests/suites/ |
| A D | test_suite_psa_crypto_low_hash.function | 54 * guaranteed to work: the core must pass a sufficiently large
143 * guaranteed to work: the core must pass a sufficiently large
|
| A D | test_suite_psa_crypto_persistent_key.function | 25 * upgrades work smoothly, so it's a stable interface nonetheless.
|
| /mbedtls/docs/architecture/testing/ |
| A 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.
|
| A 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/3rdparty/everest/ |
| A D | README.md | 5 …ms are supported, although the version in `everest/library/legacy` should work on most systems. Th…
|
| /mbedtls/docs/proposed/ |
| A D | psa-driver-integration-guide.md | 4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.**
|
| A D | psa-driver-developer-guide.md | 4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.**
|
| A 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…
225 …rent designs. Is there serious potential for confusion? Do we understand how the combinations work?
|
| /mbedtls/scripts/data_files/ |
| A D | query_config.fmt | 84 * WARNING: This does not work for expanding function-like macros. However,
|
| /mbedtls/docs/architecture/ |
| A 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:
|