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

[Netty 5] Early data for TLSv1.3 #8539

Open
normanmaurer opened this issue Nov 13, 2018 · 6 comments
Open

[Netty 5] Early data for TLSv1.3 #8539

normanmaurer opened this issue Nov 13, 2018 · 6 comments
Assignees
Projects

Comments

@normanmaurer
Copy link
Member

TLSv1.3 supports the concept of early data. We should add support for it.

@normanmaurer normanmaurer added this to To do in Netty 5 via automation Nov 13, 2018
@rkapsi
Copy link
Member

rkapsi commented Nov 13, 2018

Is there anything special that needs to happen other than using Session Tickets (or IDs) in conjunction with TLS 1.3? I'm speaking in terms of server side, a client might require some extra work.

@rkapsi
Copy link
Member

rkapsi commented Nov 19, 2018

Adding link to this SSL_read_early_data for future reference.

@rkapsi
Copy link
Member

rkapsi commented Nov 20, 2018

@normanmaurer I'd like to take a stab at this.

@rkapsi rkapsi moved this from To do to In progress in Netty 5 Nov 20, 2018
@rkapsi rkapsi self-assigned this Nov 20, 2018
@rkapsi
Copy link
Member

rkapsi commented Nov 27, 2018

To give a little update. The TCN side is pretty straight forward. BoringSSL uses a slightly different API than OpenSSL but I believe Boring's API can be "massaged" to emulate the OpenSSL API/behavior. I have that stuff compiling and hypothetically working.

Now, SSLEngine#wrap/unwrap is where the skeletons lie. I'm afraid none of the state and logic flow hold in the context of early data. It'll take a few 🍷 to untangle it.

@rkapsi rkapsi moved this from In progress to To do in Netty 5 Mar 21, 2019
@hyperxpro
Copy link
Contributor

@rkapsi Any updates?

@hyperxpro
Copy link
Contributor

Also, we need a way to notify SslHandler that TLS was established using the Early Data method. Because there are some weaknesses to this. Maybe something like SslHandler#isEarlyData would do the job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Netty 5
  
To do
Development

No branches or pull requests

3 participants