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.

Sign up for GitHub

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

Jump to bottom

Can we add a test vector for ChaCha20 header protection? #3488

Closed
marten-seemann opened this issue Mar 2, 2020 · 1 comment · Fixed by #3712
Closed

Can we add a test vector for ChaCha20 header protection? #3488

marten-seemann opened this issue Mar 2, 2020 · 1 comment · Fixed by #3712
Labels
-tls editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing

Comments

@marten-seemann
Copy link
Contributor

I recently messed this up in my implementation, and there's no test vector that could have saved me.
@marten-seemann marten-seemann changed the title Can we add a test vector for ChaCha20 header encryption? Can we add a test vector for ChaCha20 header protection? Mar 2, 2020
@martinthomson martinthomson added -tls editorial An issue that does not affect the design of the protocol; does not require consensus. labels Mar 2, 2020
@martinthomson
Copy link
Member

[patch-needed]

I think that it should be possible with a tweak to the javascript file we have to do this. But I would appreciate some help with that.

@larseggert larseggert added this to Triage in Late Stage Processing via automation Mar 3, 2020
@LPardue LPardue moved this from Triage to Editorial Issues in Late Stage Processing Mar 3, 2020
@ueno ueno mentioned this issue Mar 10, 2020
Closed
martinthomson added a commit that referenced this issue Jun 2, 2020
@martinthomson
Example of ChaCha20-Poly1305
ee88574 
This uses a packet with a short header because a) we don't have an
example of that already; b) that gives me an opportunity to show what
the different key derivations look like, including key updates; and c)
this example won't need to be updated when the draft number changes, or
even when the final spec is complete.

Closes #3488.
@martinthomson martinthomson mentioned this issue Jun 2, 2020
Merged
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-tls editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Example of ChaCha20-Poly1305 quicwg/base-drafts
2 participants
@martinthomson @marten-seemann