Skip to content

Commit 38009f7

Browse files
committed
Xref interruptible operations from key usage flags
1 parent acd80e3 commit 38009f7

1 file changed

Lines changed: 10 additions & 2 deletions

File tree

doc/crypto/api/keys/policy.rst

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -180,6 +180,7 @@ The usage flags are encoded in a bitmask, which has the type `psa_key_usage_t`.
180180
* `psa_mac_compute()`
181181
* `psa_mac_sign_setup()`
182182
* `psa_sign_message()`
183+
* `psa_sign_interruptible_setup()`, when signing a message.
183184

184185
For a key pair, this concerns the private key.
185186

@@ -194,6 +195,7 @@ The usage flags are encoded in a bitmask, which has the type `psa_key_usage_t`.
194195
* `psa_mac_verify()`
195196
* `psa_mac_verify_setup()`
196197
* `psa_verify_message()`
198+
* `psa_verify_interruptible_setup()`, when verifying the signature of a message.
197199

198200
For a key pair, this concerns the public key.
199201

@@ -203,7 +205,10 @@ The usage flags are encoded in a bitmask, which has the type `psa_key_usage_t`.
203205
.. summary::
204206
Permission to sign a message hash with the key.
205207

206-
This flag is required to use the key to sign a message hash in an asymmetric signature operation. The flag must be present on keys used when calling `psa_sign_hash()`.
208+
This flag is required to use the key to sign a pre-computed message hash in an asymmetric signature operation. The flag must be present on keys used with the following APIs:
209+
210+
* `psa_sign_hash()`
211+
* `psa_sign_interruptible_setup()` when signing a pre-computed hash.
207212

208213
This flag automatically sets `PSA_KEY_USAGE_SIGN_MESSAGE`: if an application sets the flag `PSA_KEY_USAGE_SIGN_HASH` when creating a key, then the key always has the permissions conveyed by `PSA_KEY_USAGE_SIGN_MESSAGE`, and the flag `PSA_KEY_USAGE_SIGN_MESSAGE` will also be present when the application queries the usage flags of the key.
209214

@@ -215,7 +220,10 @@ The usage flags are encoded in a bitmask, which has the type `psa_key_usage_t`.
215220
.. summary::
216221
Permission to verify a message hash with the key.
217222

218-
This flag is required to use the key to verify a message hash in an asymmetric signature verification operation. The flag must be present on keys used when calling `psa_verify_hash()`.
223+
This flag is required to use the key to verify a pre-computed message hash in an asymmetric signature verification operation. The flag must be present on keys used with the following APIs:
224+
225+
* `psa_verify_hash()`
226+
* `psa_verify_interruptible_setup()`, when verifying the signature of a pre-computed hash.
219227

220228
This flag automatically sets `PSA_KEY_USAGE_VERIFY_MESSAGE`: if an application sets the flag `PSA_KEY_USAGE_VERIFY_HASH` when creating a key, then the key always has the permissions conveyed by `PSA_KEY_USAGE_VERIFY_MESSAGE`, and the flag `PSA_KEY_USAGE_VERIFY_MESSAGE` will also be present when the application queries the usage flags of the key.
221229

0 commit comments

Comments
 (0)