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

TLS 1.3 #592

Closed
kazu-yamamoto opened this issue Nov 22, 2016 · 6 comments
Closed

TLS 1.3 #592

kazu-yamamoto opened this issue Nov 22, 2016 · 6 comments
Assignees
Labels

Comments

@kazu-yamamoto
Copy link
Contributor

TLS 1.3 is being standardized in IETF.
Note that the version would be renamed in the future.

In my local branches, TLS 1.3 is working for Warp:

  • cryptonite - this PR introduces a new API for elliptic curve diffie hellman. It enables C-based P256 backend, Haskell P384/P521 and C-based X25519.
  • tls - this branch is for TLS 1.3
  • Warp - this branch is for TLS 1.3

Now, I have implemented TLS 1.3 ID 18 in the server side only:

  • Full negotiation is tested with picotls, Firefox Nightly and Google Canary
  • Hello retry request is tested with Google Canary (X25519 -> P256)

I'm now trying to implement:

  • PSK (pre-shared symmetric key) including resumption
  • 0RTT
  • The client side
@kazu-yamamoto
Copy link
Contributor Author

PSK is done.
I'm going to try 0RTT.

@kazu-yamamoto
Copy link
Contributor Author

0RTT is done.

@kazu-yamamoto kazu-yamamoto self-assigned this Dec 6, 2016
@kazu-yamamoto
Copy link
Contributor Author

Client full handshake: done.
Client hello retry request: done.

@kazu-yamamoto
Copy link
Contributor Author

The merge process of cryptonite: done.

@kazu-yamamoto
Copy link
Contributor Author

Client HRR and 0RTT: done.

@kazu-yamamoto
Copy link
Contributor Author

I decided to maintain haskell-tls/hs-tls#167 instead of this issue.

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

No branches or pull requests

2 participants