commit | 283d3e3744d74b0dc1e05c96680eac9803a01be2 | [log] [tgz] |
---|---|---|
author | Christian Huitema <huitema@huitema.net> | Sun Mar 31 22:35:11 2019 -0700 |
committer | GitHub <noreply@github.com> | Sun Mar 31 22:35:11 2019 -0700 |
tree | 3147564a6f76678a067aa2c7fb4e2ced09cebc8d | |
parent | 15e9c4dd068954868eec96a455ebd928c67d65c2 [diff] | |
parent | ee70003aba99f670f391b8e809247bbe7e4595b5 [diff] |
Merge pull request #42 from h2o/master Add ptlsbench fixes
Picotls is a TLS 1.3 (RFC 8446) implementation written in C, with the following features:
Primary goal of the project is to create a fast, tiny TLS 1.3 implementation that can be used with the HTTP/2 protocol stack and possibly the upcoming QUIC stack of the H2O HTTP/2 server.
The TLS protocol ipmlementation of picotls is licensed under the MIT license.
License and the cryptographic algorithms supported by the crypto bindings are as follows:
Binding | License | Key Exchange | Certificate | AEAD cipher |
---|---|---|---|---|
minicrypto | CC0 / 2-clause BSD | secp256r1, x25519 | ECDSA (P256)1 | AES-128-GCM, chacha20-poly1305 |
OpenSSL | OpenSSL | secp256r1, secp384r1, secp521r1, x25519 | RSA, ECDSA (P256) | AES-128-GCM, chacha20-poly1305 |
Note 1: Minicrypto binding is capable of signing a handshake using the certificate's key, but cannot verify a signature sent by the peer.
If you have cloned picotls from git then ensure that you have initialised the submodules:
% git submodule init % git submodule update
Build using cmake:
% cmake . % make % make check
A dedicated documentation for using picotls with Visual Studio can be found in WindowsPort.md.
Developer documentation should be available on the wiki.
Run the test server (at 127.0.0.1:8443):
% ./cli -c /path/to/certificate.pem -k /path/to/private-key.pem 127.0.0.1 8443
Connect to the test server:
% ./cli 127.0.0.1 8443
Using resumption:
% ./cli -s session-file 127.0.0.1 8443
The session-file is read-write. The cli server implements a single-entry session cache. The cli server sends NewSessionTicket when it first sends application data after receiving ClientFinished.
Using early-data:
% ./cli -s session-file -e 127.0.0.1 8443
When -e
option is used, client first waits for user input, and then sends CLIENT_HELLO along with the early-data.
The software is provided under the MIT license. Note that additional licences apply if you use the minicrypto binding (see above).