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

Upstream TLS 1.3 state machine logic #4329

Closed
hanno-becker opened this issue Apr 10, 2021 · 1 comment · Fixed by #4942
Closed

Upstream TLS 1.3 state machine logic #4329

hanno-becker opened this issue Apr 10, 2021 · 1 comment · Fixed by #4942
Assignees
Labels

Comments

@hanno-becker
Copy link

Task: Study whether it is possible to upstream the core TLS 1.3 state machine logic without at the same time upstreaming each handshake state handler. Ideally, we upstream the frame first and then insert the state handlers one message a time.

At the time of writing, it's not yet clear to me how feasible this is, but as a monolithic PR upstreaming the entire TLS 1.3 state machine with all state handlers at once is certainly not desirable, it's worth exploring at least.

@hanno-becker hanno-becker added the size-m Estimated task size: medium (~1w) label Apr 26, 2021
@bensze01 bensze01 modified the milestone: TLS 1.3 MVP Jul 28, 2021
@bensze01 bensze01 removed this from the TLS 1.3 MVP milestone Aug 11, 2021
@yuhaoth yuhaoth self-assigned this Sep 3, 2021
@mpg
Copy link
Contributor

mpg commented Sep 3, 2021

As discussed today with @ronald-cron-arm and @yuhaoth we decided to not upstream the state machine separately, but do each step as we implement the corresponding step in the handshake. Hence closing this issue, as the work will be covered by other issues.

@mpg mpg closed this as completed Sep 3, 2021
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 a pull request may close this issue.

4 participants