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

Possibility to choose TLS library #68

Open
kriskwiatkowski opened this issue Aug 3, 2019 · 0 comments
Open

Possibility to choose TLS library #68

kriskwiatkowski opened this issue Aug 3, 2019 · 0 comments

Comments

@kriskwiatkowski
Copy link

What?

  • httperf could be useful to test TLS performance
  • Currently httperf uses OpenSSL. OpenSSL and BoringSSL have very similar API. Maybe it could be possible to have compile time switch allowing to use both libraries

Why?

  • BoringSSL offers some other, different functionalities. Recently it has added support for 2 post-quantum key exchange algorithms. httperf could be used to measure differences between classical key exchange and post-quantum key exchange algorithms
  • PoC of BoringSSL integration + some additional features (like possibility to specify key exchange algorithm to use in TLSv1.3) can be found here:
    https://github.com/post-quantum-cryptography/httperf/tree/pq

Questions:

  • Is work in PoC interesting? Does it make sense to upstream changes?
  • Is httperf team interested in maintaining support for 2 TLS libraries?
@kriskwiatkowski kriskwiatkowski changed the title Layer allowing to use BoringSSL and OpenSSL Possibility to choose TLS library Aug 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant