Possibility to choose TLS library #68

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?