Searched refs:fallback (Results 1 – 11 of 11) sorted by relevance
/mbedtls-3.5.0/tests/suites/ |
D | test_suite_psa_crypto_driver_wrappers.data | 5 sign_hash transparent driver: fallback ECDSA SECP256R1 SHA-256 21 sign_hash transparent driver: fallback RSA PKCS#1 v1.5, raw 37 sign_hash transparent driver: fallback RSA PKCS#1 v1.5 SHA-256 53 verify_hash transparent driver: fallback ECDSA SECP256R1 SHA-256 65 verify_hash transparent driver: fallback Public Key ECDSA SECP256R1 SHA-256 77 verify_hash transparent driver: fallback Key Pair RSA PKCS#1 v1.5 raw 89 verify_hash transparent driver: fallback Key Pair RSA PKCS#1 v1.5 SHA-256 101 verify_hash transparent driver: fallback Public Key RSA PKCS#1 v1.5 SHA-256 113 verify_hash transparent driver: fallback Public Key RSA-1024 PSS SHA-256 125 verify_hash transparent driver: fallback Public Key RSA-1024 PSS-any-salt SHA-256 [all …]
|
/mbedtls-3.5.0/scripts/data_files/driver_templates/ |
D | psa_crypto_driver_wrappers.c.jinja | 157 /* Declared with fallback == true */ 230 /* Declared with fallback == true */ 317 /* Declared with fallback == true */ 401 /* Declared with fallback == true */ 506 /* Declared with fallback == true */ 606 /* Declared with fallback == true */ 815 /* Declared with fallback == true */ 822 /* Software fallback */ 1177 /* Declared with fallback == true */ 1265 /* Declared with fallback == true */ [all …]
|
/mbedtls-3.5.0/docs/architecture/psa-migration/ |
D | testing.md | 25 via PSA while some others weren't, with a run-time fallback. In this case, it's 27 right decision was made at run-time, i. e. that we didn't use the fallback for
|
D | md-cipher-dispatch.md | 151 * must not call PSA (or must have a fallback) if their caller is not in the PSA domain and the PSA …
|
/mbedtls-3.5.0/docs/proposed/ |
D | psa-conditional-inclusion-c.md | 22 …ce the built-in implementation of a cryptographic mechanism (or, with **fallback**, the built-in i… 32 … TLS build must not include the corresponding software code (unless a software fallback is needed). 113 * **`MBEDTLS_PSA_ACCEL_xxx`** indicates whether a fully-featured, fallback-free transparent driver … 140 …EDTLS_PSA_ACCEL_xxx` symbols according to the availability of transparent drivers without fallback.
|
D | psa-driver-interface.md | 39 [Req.fallback] Accelerator drivers can specify that they do not fully support a cryptographic mecha… 97 …fallback"` (optional for transparent drivers, not permitted for opaque drivers, boolean). If prese… 121 …list](#driver-description-list) is invoked. If the capability has [fallback](#fallback) enabled an… 334 - otherwise, or on fallback, the core uses its built-in implementation. 750 …ed if the driver specification for random generation has the [fallback property](#fallback) enable… 756 …driver-description-capability) partially, by setting the capability's `"fallback"` property to tru… 758 If a transparent driver entry point is part of a capability which has a true `"fallback"` property … 760 If all the available drivers have fallback enabled and return `PSA_ERROR_NOT_SUPPORTED`, the core w… 763 If a transparent driver entry point is part of a capability where the `"fallback"` property is fals… 1093 …one? The last one? Unspecified? Or is this an error (excluding capabilities with fallback enabled)?
|
/mbedtls-3.5.0/docs/architecture/testing/ |
D | driver-interface-test-strategy.md | 127 #### Requirements for fallback 129 The driver interface includes a fallback mechanism so that a driver can reject a request at runtime…
|
/mbedtls-3.5.0/docs/architecture/ |
D | psa-crypto-implementation-structure.md | 50 …_verify() API could call first psa_driver_wrapper_mac_verify() and then fallback to psa_driver_wra…
|
/mbedtls-3.5.0/programs/ssl/ |
D | ssl_client2.c | 536 int fallback; /* is this a fallback connection? */ member 961 opt.fallback = DFL_FALLBACK; in main()
|
/mbedtls-3.5.0/docs/ |
D | 3.0-migration-guide.md | 646 for fallback SCSV (RFC 7507) was also removed. There is no migration path as
|
/mbedtls-3.5.0/ |
D | ChangeLog | 109 implementation as a fallback for when the assembly one cannot be used. 1089 CBC record splitting, fallback SCSV, and the ability to configure 1367 * Automatic fallback to a software implementation of ECP when
|