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

Adding TLSv1.3 in wolfSSL #2349

Closed
wants to merge 1 commit into from
Closed

Adding TLSv1.3 in wolfSSL #2349

wants to merge 1 commit into from

Conversation

kawuun
Copy link

@kawuun kawuun commented Mar 1, 2018

Tested:

tls1.3 - draft 21

./src/curl -I -v --tlsv1.3 https://tls13.akamai.io/

  • Trying 2a02:26f0:d8:385::5f37...
  • TCP_NODELAY set
  • Connected to tls13.akamai.io (2a02:26f0:d8:385::5f37) port 443 (#0)
  • successfully set certificate verify locations:
  • CAfile: /etc/ssl/certs/ca-certificates.crt
    CApath: none
  • ALPN, offering http/1.1
  • ALPN, server accepted to use http/1.1
  • SSL connection using TLSv1.3 / TLS13-AES256-GCM-SHA384

HEAD / HTTP/1.1
Host: tls13.akamai.io
User-Agent: curl/7.59.0-DEV
Accept: /

< HTTP/1.1 200 OK
HTTP/1.1 200 OK

tls1.3 - draft 18

./src/curl -I -v --tlsv1.3 https://h2o.examp1e.net

  • Trying 133.242.206.244...
  • TCP_NODELAY set
  • Connected to h2o.examp1e.net (133.242.206.244) port 443 (#0)
  • successfully set certificate verify locations:
  • CAfile: /etc/ssl/certs/ca-certificates.crt
    CApath: none
  • ALPN, offering http/1.1
  • ALPN, server accepted to use http/1.1
  • SSL connection using TLSv1.3 / TLS13-AES128-GCM-SHA256

HEAD / HTTP/1.1
Host: h2o.examp1e.net
User-Agent: curl/7.59.0-DEV
Accept: /

< HTTP/1.1 200 OK
HTTP/1.1 200 OK

Copy link
Member

@bagder bagder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A nice and clean small patch. I like!

@bagder bagder added the TLS label Mar 1, 2018
@bagder
Copy link
Member

bagder commented Mar 4, 2018

Thanks!

@bagder bagder closed this in 613ccbf Mar 4, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

Successfully merging this pull request may close these issues.

None yet

2 participants