1. 29 7月, 2016 7 次提交
    • M
      Fix BIO_pop for SSL BIOs · b46fe860
      Matt Caswell 提交于
      The BIO_pop implementation assumes that the rbio still equals the next BIO
      in the chain. While this would normally be the case, it is possible that it
      could have been changed directly by the application. It also does not
      properly cater for the scenario where the buffering BIO is still in place
      for the write BIO.
      
      Most of the existing BIO_pop code for SSL BIOs can be replaced by a single
      call to SSL_set_bio(). This is equivalent to the existing code but
      additionally handles the scenario where the rbio has been changed or the
      buffering BIO is still in place.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      b46fe860
    • M
      Fix BIO_push ref counting for SSL BIO · eddef305
      Matt Caswell 提交于
      When pushing a BIO onto an SSL BIO we set the rbio and wbio for the SSL
      object to be the BIO that has been pushed. Therefore we need to up the ref
      count for that BIO. The existing code was uping the ref count on the wrong
      BIO.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      eddef305
    • M
      Don't double free the write bio · 8e3854ac
      Matt Caswell 提交于
      When setting the read bio we free up any old existing one. However this can
      lead to a double free if the existing one is the same as the write bio.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      8e3854ac
    • M
      Add a test for SSL_set_bio() · 7fb4c820
      Matt Caswell 提交于
      The SSL_set_bio() function has some complicated ownership rules. This adds a
      test to make sure it all works as expected.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      7fb4c820
    • M
      Make the checks for an SSLv2 style record stricter · 0647719d
      Matt Caswell 提交于
      SSLv2 is no longer supported in 1.1.0, however we *do* still accept an SSLv2
      style ClientHello, as long as we then subsequently negotiate a protocol
      version >= SSLv3. The record format for SSLv2 style ClientHellos is quite
      different to SSLv3+. We only accept this format in the first record of an
      initial ClientHello. Previously we checked this by confirming
      s->first_packet is set and s->server is true. However, this really only
      tells us that we are dealing with an initial ClientHello, not that it is
      the first record (s->first_packet is badly named...it really means this is
      the first message). To check this is the first record of the initial
      ClientHello we should also check that we've not received any data yet
      (s->init_num == 0), and that we've not had any empty records.
      
      GitHub Issue #1298
      Reviewed-by: NEmilia Käsper <emilia@openssl.org>
      0647719d
    • R
      Various doc fixes. · 1a627771
      Rich Salz 提交于
      Cannot nest B<> tags
      Document "openssl speed" command.
      Fix doc nits: missing NAME/SYNOPSIS stuff
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      1a627771
    • E
      Add memory sanitizer config, and run on travis. · 29df3061
      Emilia Kasper 提交于
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      29df3061
  2. 27 7月, 2016 5 次提交
  3. 26 7月, 2016 8 次提交
  4. 25 7月, 2016 20 次提交