-
Notifications
You must be signed in to change notification settings - Fork 68
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
Add references to RFC 4493 in comments about AesCMac. #184
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very much fine 👍
Thanks for your contributions!
Ugh, it seems merging some other PR broke yours. Would you be able to resolve it? If not please say we can assist. Thanks! 👋 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the patch!
One thing I'm thinking about, actually - though not for this PR - is that maybe we can integrate Wycheproof in our tests, rather than having to manage our own list of test vectors. I'll raise an issue to track this :)
Wow, this looks highly relevant! Thanks for linking. |
@xaqq could you please rebase and resolve the conflicts so that we can merge the PR? :) |
Signed-off-by: Arnaud Kapp <[email protected]>
Thanks for your time @xaqq! |
Hello,
Thanks for merging previous PR exposing AesCMac.
Test vectors were coming from RFC 4493 so this commit clarifies that.
(Also performs the test against the 4 available test data of the RFC)