1. 02 8月, 2016 2 次提交
  2. 01 8月, 2016 24 次提交
  3. 31 7月, 2016 7 次提交
  4. 30 7月, 2016 5 次提交
  5. 29 7月, 2016 2 次提交
    • M
      Update the SSL_set_bio()/SSL_set0_rbio()/SSL_set0_wbio() docs · e040a42e
      Matt Caswell 提交于
      Update the documentation for the newly renamed and modified SSL_set0_rbio()
      and SSL_set0_wbio() functions. State that they should be preferred over
      SSL_set_bio(). Attempt to document the ownership rules for SSL_set_bio().
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      e040a42e
    • M
      Simplify and rename SSL_set_rbio() and SSL_set_wbio() · 65e2d672
      Matt Caswell 提交于
      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: NRich Salz <rsalz@openssl.org>
      65e2d672