Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processing unauthenticated AEAD data #4

Closed
nwalfield opened this issue May 19, 2020 · 1 comment
Closed

Processing unauthenticated AEAD data #4

nwalfield opened this issue May 19, 2020 · 1 comment

Comments

@nwalfield
Copy link

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.

Unfortunately, RNP does this as does gpg.

@hannob
Copy link
Owner

hannob commented May 20, 2020

Ultimately this is somewhat "variations of efail", but probably deserves to be mentioned explicitly.

@hannob hannob closed this as completed in 73599fd May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants