Lines Matching refs:work
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:
92 * Make non-covered modules call PSA, but only [when this will actually work](#why-psa-is-not-always…
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:…
254 …rt. So `MBEDTLS_SHA256_C` must imply support for RSA-PSS-SHA-256. It must work at all times, regar…
258 …A's SHA-256 comes from an accelerator driver), then SHA-256 only needs to work if `psa_crypto_init…
267 …me the driver is initialized; we've [considered requiring hash drivers to work without initializat…
298 * Mixed-domain code can assume that PSA buffer calculations work correctly for all algorithms that …
354 …ncrypt direction. Currently, GCM and CCM use the Cipher layer in order to work with AES, Aria and …
357 …xtend it to other block ciphers at the moment), while GCM and CCM need to work with 3 block cipher…
380 - or more work to apply the simplifications to all of Cipher.
564 The architecture can be extended to support `MBEDTLS_PSA_CRYPTO_CLIENT` with a little extra work. H…