-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Security
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The server's vendored version of ASIO was upgraded in SPM-4010.
However, we don't use the vendored ASIO for TLS (SSL). Instead, we have a older copied version of ASIO's SSL implementation in-tree, which we have since modified.
This means that when we upgrade the vendored ASIO, we are not upgrading the SSL portions of the code.
There is a correspondence between our in-tree SSL code and the upstream ASIO's, e.g. our mongo/util/net/ssl/stream.hpp and upstream's asio/ssl/stream.hpp.
This Jira issue is to audit whether any of our ASIO-based SSL code would benefit from being brought up to date with the newly upgraded vendored ASIO.
Note that ASIO's SSL code is excluded from third_party/asio, in order to avoid confusion.