@nodejs/releasers Might affect release plans, though I'm still not convinced that issue affects Node.js, we only saw it when interacting with openssl s_client/s_server, which had a bug in their implementation that became noticable after the behaviour change in OpenSSL 1.1.1e.
Still, with all the release delays, its likely that 1.1.1f can go out in place of 1.1.1e 10.x. I don't recall from memory the current state of release plans for 12 and 13, I'll check them out Monday (if no one beats me to it).
@hassaanp Interested in doing this update? It really should be trivial, compared to the last one! (famous last words...).
The text was updated successfully, but these errors were encountered:
sam-github commentedMar 28, 2020
Yes, another one! :-)
https://mta.openssl.org/pipermail/openssl-announce/2020-March/000168.html
Looks like its related to the EOF detection issue:
#32210 (comment)
@nodejs/releasers Might affect release plans, though I'm still not convinced that issue affects Node.js, we only saw it when interacting with
openssl s_client/s_server
, which had a bug in their implementation that became noticable after the behaviour change in OpenSSL 1.1.1e.Still, with all the release delays, its likely that 1.1.1f can go out in place of 1.1.1e 10.x. I don't recall from memory the current state of release plans for 12 and 13, I'll check them out Monday (if no one beats me to it).
@hassaanp Interested in doing this update? It really should be trivial, compared to the last one! (famous last words...).
The text was updated successfully, but these errors were encountered: