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
This note reports a small flaw in the security proof of OCB3 that
may cause a loss of security in practice, even if OCB3 is correctly implemented in a trustworthy
and nonce-respecting module. The flaw is present when OCB3 is used with short nonces. It has
security implications that are worse than nonce-repetition as confidentiality and authenticity are
lost until the key is changed. The flaw is due to an implicit condition in the security proof and to
the way OCB3 processes nonce.
It makes the following recommendation:
In the case of OCB3, it is easy to fix the algorithm’s specification in order to avoid the
weakness and abide to the full assumptions of the security proof. If the description is unchanged,
the requirement N ≥ 6 must become an absolute requirement.
We should update the bounds on the nonce size accordingly.
The text was updated successfully, but these errors were encountered:
This paper presents an attack on OCB3 with short nonces:
https://eprint.iacr.org/2023/326.pdf
It makes the following recommendation:
We should update the bounds on the nonce size accordingly.
The text was updated successfully, but these errors were encountered: