tlsfuzzer/tlslite-ng

Early handshake return in TLS1.3

Open

#288 opened on Jul 3, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (95 forks)auto 404
complexenhancementhelp wanted

Repository metrics

Stars
 (269 stars)
PR merge metrics
 (PR metrics pending)

Description

In TLS1.3 the server can finish handshaking right after sending Finished message (if it didn't ask for client certificates), this will allow the application to send data right after the Finished, or NewSessionTicket. Especially useful for HTTP/2 early data push or reply to 0-RTT request.

Contributor guide

Research direction
Study the TLS 1.3 handshake implementation in tlslite ng, particularly the server side handling after sending Finished. Identify where the early return can be inserted to allow sending application data or NewSessionTicket without waiting for client response. Look at existing handshake state machine and modify it to support early completion when no client certificate is requested.
Tech stack
python
Domain
securitybackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitTLS knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50