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
As defined by 4880bis, AEAD can have very large (exabyte-sized) chunks. This leaves implementations with two choices: fail to buffer large chunks and thereby fail to parse the message, or process unauthenticated data. Many people argue and it has been codified in RFC 5116 (Section 2.2) that unauthenticated data should not be processed:
[The authenticated decryption operation]
has only a single output, either a plaintext value P or a special
symbol FAIL that indicates that the inputs are not authentic.
As defined by 4880bis, AEAD can have very large (exabyte-sized) chunks. This leaves implementations with two choices: fail to buffer large chunks and thereby fail to parse the message, or process unauthenticated data. Many people argue and it has been codified in RFC 5116 (Section 2.2) that unauthenticated data should not be processed:
Unfortunately, RNP does this as does gpg.
The text was updated successfully, but these errors were encountered: