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

fix: allow for clock skew in resumption #4650

Merged
merged 9 commits into from
Jul 25, 2024
Merged

Conversation

jmayclin
Copy link
Contributor

@jmayclin jmayclin commented Jul 16, 2024

Description of changes:

s2n-tls is currently unable to resume session tickets if they were issued in the "future" from the perspective of the resuming host. This means that if there is any relatively significant clock skew between the resuming host and the issuing host, the resumption attempt will fail.

This PR changes that behavior to allow session tickets to be resumed if they were issued in the "future". We are making the assumption that the clock skew is less than one week, which seems reasonable.

Testing:

modified test to assert on new behavior

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions github-actions bot added the s2n-core team label Jul 16, 2024
@jmayclin jmayclin marked this pull request as ready for review July 16, 2024 16:51
tls/s2n_resume.c Outdated Show resolved Hide resolved
- sanity check the amount of clock skew
@jmayclin jmayclin requested a review from lrstewart July 16, 2024 18:52
- typo, spelling is hard :'(
- add hard cap for clock skew at 1 hour
- okay, I actually went through a lot of work to undo this assuming that
  my local clang format was just being weird, but this is what it
insists on
@jmayclin jmayclin enabled auto-merge (squash) July 23, 2024 22:40
@jmayclin jmayclin merged commit 390d796 into aws:main Jul 25, 2024
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants