| breadcrumb |
|---|
Roadmap |
This document is the OpenSSL project roadmap. It is a living document and is expected to change over time. Objectives and dates should be considered aspirational.
Some of these objectives can be achieved more easily and quickly than others.
OpenSSL is taking a multi-staged approach to the implementation of the QUIC transport protocol:
-
For OpenSSL 3.2, the focus is on providing a client side single stream QUIC implementation.
-
OpenSSL 3.3 will follow approximately six months later implementing more of the protocol.
-
OpenSSL 3.4 aims to complete the implementation a further six months later.
-
OpenSSL 3.0 FIPS Provider has had its FIPS 140-2 validation certificate issued. See the [blog post]: https://www.openssl.org/blog/blog/2022/08/24/FIPS-validation-certificate-issued/
-
The OpenSSL 3.1 release will be about FIPS 140-3 validation submission. See the [blog post]: https://www.openssl.org/blog/blog/2022/09/30/fips-140-3/
A cryptographic algorithm needs to be defined by a national or international standard before it will be considered for inclusion into OpenSSL. Although, there is work in progress to select post-quantum algorithms for standardisation, currently none have been. OpenSSL will not be including any of the candidate algorithms until the selection process is complete.
For those interested in using the proposed algorithms now, the Open Quantum Safe project has written a provider for OpenSSL 3.x which includes the candidates.
There are a number of pull requests which represent substantial features. Each will require a significant time investment by the project's contractors to review before they can be included in OpenSSL. These features should be included gradually over upcoming releases.
- Argon2 KDFs (RFC 9106; openssl/openssl#12255 & openssl/openssl#12256)
- Attribute Certificates (RFC 5755; openssl/openssl#15857)
- Hybrid Public Key Encryption (RFC 9180; openssl/openssl#17172)
- Raw Public Keys (RFC 7250; openssl/openssl#16620)