Hi, https://www.boost.org/users/history/version_1_80_0.html, "Asio" section, states: "Fixed compatibility with OpenSSL 3.0.4 and later." However, API-s which were deprecated in openSSL 3 still exist in boost_1_80_0.tar.gzhttps://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/boost_1_80_... --> boost/asio/ssl/impl/context.ipp: · RSA_free · DH_free · d2i_RSAPrivateKey_bio · PEM_read_bio_RSAPrivateKey · SSL_CTX_use_RSAPrivateKey · SSL_CTX_use_RSAPrivateKey_file · PEM_read_bio_DHparams Is there a plan to update them? BTW - It is possible to build an application with these deprecated API-s by using CFLAGS += -Wno-deprecated-declarations, but in my understanding it is not acceptable for FIPS compliance. Thanks! ------------------------------------------- This message is confidential. If you believe you received this message in error, please inform the sender and delete this message and all attachments.
Hi Ofer,
From: Boost-users
On Behalf Of Ofer Lent via Boost-users Sent: Tuesday, 3 January 2023 16:00 To: boost-users@lists.boost.org Cc: Ofer Lent Subject: [Boost-users] ASIO openSSL 3 support [...] However, API-s which were deprecated in openSSL 3 still exist in https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/boost_1_80_... → boost/asio/ssl/impl/context.ipp: • RSA_free • DH_free • d2i_RSAPrivateKey_bio • PEM_read_bio_RSAPrivateKey • SSL_CTX_use_RSAPrivateKey • SSL_CTX_use_RSAPrivateKey_file • PEM_read_bio_DHparams
Is there a plan to update them?
All of these symbols are only used for (OPENSSL_VERSION_NUMBER < 0x30000000L), so it should already work fine for OpenSSL 3.0 and later. Marcel
participants (2)
-
Marcel Raad
-
Ofer Lent