Closed ReverseControl closed 4 years ago
Your edit is correct in that you want to chose a particular KEX, and OQS used OQSKEX as a standard prefix to distinguish their ciphersuites from the ones in mainline OpenSSL. In this case they are key exchange (KEX) algorithms, not key encapsulation methods (KEMs), so the nomenclature is correct in this case. But more importantly, those strings are coming from OQS-OpenSSL and are beyond our ability to control.
Be advised that we discovered, after our release, that most Picnic certificates don't actually work because they're too large. They worked early in our testing when they were trivial, but when we started adding more fields to the certificate we found they ended up exceeded a hardcoded limit somewhere inside OpenSSL. Since protecting the data in transit from future quantum attackers is the more interesting scenario right now instead of protecting the authentication against a quantum-enabled adversary, we're leaving this for now and focusing on getting the next release ready, and recommending people still use RSA or ECDSA certificates for authentication until then. See #6 for more information.
Closing due to no further activity in a week; feel free to reopen if you have more questions on this.
The "PQCrypto-VPN/openvpn/config" folder contains examples on how to enable any available QCipherSuite:
How can I specify what KEM or QSIGNATURE PQCrypto-VPN should use? Thanks.
EDIT 1: I just realized that KEMs are part of the Cipher Suite, but they are coded as KEX, or more precisely as "OQSKEX" which is slightly confusing. "OQSKEM" would be better. Any notes on how to use the QSIGNATURE in the vpn would still be valuable though.
Here for reference, the available traditional and quantum cipher suites.: