Bug #12069
closed
[PATCH] document OpenSSL::SSL::SSLContext#setup as MT-unsafe
Added by normalperson (Eric Wong) over 8 years ago.
Updated over 8 years ago.
Description
document OpenSSL::SSL::SSLContext#setup as MT-unsafe
On a cursory inspection, using rb_block_call for extra_chain_cert
is thread-unsafe. There may be other instances of thread-unsafe
behavior in this method, but one is enough.
- ext/openssl/ossl_ssl.c (ossl_sslctx_setup): document as MT-unsafe
Files
- Status changed from Open to Closed
Applied in changeset r54097.
document OpenSSL::SSL::SSLContext#setup as MT-unsafe
On a cursory inspection, using rb_block_call for extra_chain_cert
is thread-unsafe. There may be other instances of thread-unsafe
behavior in this method, but one is enough.
Committed with a minor wording change as r54097
s/SSLSockets/SSLSocket objects/ for searchability
- Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN to 2.1: REQUIRED, 2.2: REQUIRED, 2.3: REQUIRED
- Backport changed from 2.1: REQUIRED, 2.2: REQUIRED, 2.3: REQUIRED to 2.1: DONE, 2.2: REQUIRED, 2.3: REQUIRED
ruby_2_1 r54282 merged revision(s) 54097.
- Backport changed from 2.1: DONE, 2.2: REQUIRED, 2.3: REQUIRED to 2.1: DONE, 2.2: DONE, 2.3: REQUIRED
Backported into ruby_2_2
branch at r54332.
- Backport changed from 2.1: DONE, 2.2: DONE, 2.3: REQUIRED to 2.1: DONE, 2.2: DONE, 2.3: DONE
ruby_2_3 r54379 merged revision(s) 54097.
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0