summaryrefslogtreecommitdiffstats
path: root/README.ENGINE
diff options
context:
space:
mode:
authorMatt Caswell <matt@openssl.org>2016-07-21 12:17:29 +0100
committerMatt Caswell <matt@openssl.org>2016-07-29 14:09:57 +0100
commit65e2d672548e7c4bcb28f1c5c835362830b1745b (patch)
tree6d87e72458317ce13c8f54aebd368b9965619525 /README.ENGINE
parent9a7169870e803bdd9767d75ca8f64802ca0e7f1c (diff)
Simplify and rename SSL_set_rbio() and SSL_set_wbio()
SSL_set_rbio() and SSL_set_wbio() are new functions in 1.1.0 and really should be called SSL_set0_rbio() and SSL_set0_wbio(). The old implementation was not consistent with what "set0" means though as there were special cases around what happens if the rbio and wbio are the same. We were only ever taking one reference on the BIO, and checking everywhere whether the rbio and wbio are the same so as not to double free. A better approach is to rename the functions to SSL_set0_rbio() and SSL_set0_wbio(). If an existing BIO is present it is *always* freed regardless of whether the rbio and wbio are the same or not. It is therefore the callers responsibility to ensure that a reference is taken for *each* usage, i.e. one for the rbio and one for the wbio. The legacy function SSL_set_bio() takes both the rbio and wbio in one go and sets them both. We can wrap up the old behaviour in the implementation of that function, i.e. previously if the rbio and wbio are the same in the call to this function then the caller only needed to ensure one reference was passed. This behaviour is retained by internally upping the ref count. This commit was inspired by BoringSSL commit f715c423224. RT#4572 Reviewed-by: Rich Salz <rsalz@openssl.org>
Diffstat (limited to 'README.ENGINE')
0 files changed, 0 insertions, 0 deletions