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

correctly handle key updates within the 3 PTO period #2787

Merged
merged 1 commit into from
Sep 22, 2020

Conversation

marten-seemann
Copy link
Member

Depends on #2781.

We need to:

  • stop the timer to drop the previous generation
  • correctly log that the N-1 keys are dropped immediately when keys are updated to N+1

@codecov
Copy link

codecov bot commented Sep 15, 2020

Codecov Report

Merging #2787 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2787      +/-   ##
==========================================
+ Coverage   86.02%   86.03%   +0.01%     
==========================================
  Files         133      133              
  Lines       12071    12077       +6     
==========================================
+ Hits        10384    10390       +6     
  Misses       1355     1355              
  Partials      332      332              
Impacted Files Coverage Δ
internal/handshake/updatable_aead.go 96.43% <100.00%> (+0.11%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 27448c1...e94db95. Read the comment docs.

We need to:
* stop the timer to drop the previous generation
* correctly log that the N-1 keys are dropped immediately when keys are
updated to N+1
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

Successfully merging this pull request may close these issues.

2 participants