Lines Matching refs:valid

77 * `"prefix"` (mandatory, string). This must be a valid, non-empty prefix for a C identifier. All th…
373 * `PSA_KEY_DERIVATION_INPUT_TYPE_BYTES`: the step is valid and present and is a transparent byte st…
374 * `PSA_KEY_DERIVATION_INPUT_TYPE_KEY`: the step is valid and present and is a byte string passed vi…
375 * `PSA_KEY_DERIVATION_INPUT_TYPE_INTEGER`: the step is valid and present and is an integer. Call `p…
403 …` to the size of the key context in bytes. The key context buffer remains valid for the duration o…
409 * `PSA_ERROR_DOES_NOT_EXIST`: the input step is valid for this particular algorithm, but it is not …
685 The pointer output by `psa_crypto_driver_pake_get_password_key` is only valid until the "pake_setup…
785 All key creation entry points must ensure that the resulting key is valid as specified in the secti…
801 …valid key data. Key data is _valid_ if operations involving the key are guaranteed to work functio…
806 * On the other hand, it is acceptable for import to accept a key that cannot be verified as valid i…
1229 …e. This pointer remains valid during a call to a driver entry point. Once the entry point returns,…
1375 …ing callbacks to the core: these functions could return a pointer that is valid until the driver e…