You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mostly.
We need to keep a limited amount of storage per AES-256-GCM key to track
usage, since these keys can only be used a certain number of times due
to their IV problems.
For HMAC, we don't specify a key usage on the output MAC, since it has
to be imported back into Caliptra to be used as a key, where its usage
will have to be specified.
We also fix a few other minor issues with the mailbox documentation:
Fixes#1753Fixes#1754Fixes#1755Fixes#1756
Mostly.
We need to keep a limited amount of storage per AES-256-GCM key to track
usage, since these keys can only be used a certain number of times due
to their IV problems.
For HMAC, we don't specify a key usage on the output MAC, since it has
to be imported back into Caliptra to be used as a key, where its usage
will have to be specified.
We also fix a few other minor issues with the mailbox documentation:
Fixes#1753Fixes#1754Fixes#1755Fixes#1756
Mostly.
We need to keep a limited amount of storage per AES-256-GCM key to track
usage, since these keys can only be used a certain number of times due
to their IV problems.
For HMAC, we don't specify a key usage on the output MAC, since it has
to be imported back into Caliptra to be used as a key, where its usage
will have to be specified.
We also fix a few other minor issues with the mailbox documentation:
Fixes#1753Fixes#1754Fixes#1755Fixes#1756
https://github.com/chipsalliance/caliptra-sw/blob/main-2.x/runtime/README.md describes
CM_ECDH_GENERATE
andCM_ECDH_FINISH
, which return and accept X/Y coordinate pairs. However, the encoding is unclear. We should specify that these are big-endian.The text was updated successfully, but these errors were encountered: