Length limits of encauth etc. #216
Labels
No labels
bug
duplicate
enhancement
feature
help wanted
improve API
invalid
needs documentation
not-planned
rtfm
stale
support
wishlist
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libtom/libtomcrypt#216
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As @karel-m pointed out in https://github.com/libtom/libtomcrypt/pull/211/files#r115594690 we have a possible issue in
chacha20poly1305We should verify the existing implementations regarding such limitations.
The following encauth implementations exist, they should be marked as resolved after their implementation has been verified and/or fixed
ccmchacha20poly1305eaxgcmfixed in #129ocbocb3Should this list contain further elements, e.g. MAC's?
CFRG is working on defining those limits in https://datatracker.ietf.org/doc/draft-irtf-cfrg-aead-limits/
Integration will be postponed until the RFC is finished.