1. 03 4月, 2016 1 次提交
  2. 30 3月, 2016 2 次提交
  3. 23 3月, 2016 3 次提交
  4. 21 3月, 2016 3 次提交
  5. 19 3月, 2016 2 次提交
  6. 18 3月, 2016 5 次提交
  7. 17 3月, 2016 1 次提交
  8. 16 3月, 2016 1 次提交
    • M
      Fix a TLSProxy race condition · 5427976d
      Matt Caswell 提交于
      TLSProxy starts s_server and specifies the number of client connects
      it should expect. After that s_server is supposed to close down
      automatically. However, if another test is then run then TLSProxy
      will start a new instance of s_server. If the previous instance
      hasn't closed down yet then the new instance can fail to bind to
      the socket.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      5427976d
  9. 12 3月, 2016 4 次提交
  10. 11 3月, 2016 4 次提交
  11. 10 3月, 2016 5 次提交
  12. 09 3月, 2016 8 次提交
  13. 08 3月, 2016 1 次提交
    • M
      Add an SSL_has_pending() function · 892b9376
      Matt Caswell 提交于
      This is similar to SSL_pending() but just returns a 1 if there is data
      pending in the internal OpenSSL buffers or 0 otherwise (as opposed to
      SSL_pending() which returns the number of bytes available). Unlike
      SSL_pending() this will work even if "read_ahead" is set (which is the
      case if you are using read pipelining, or if you are doing DTLS). A 1
      return value means that we have unprocessed data. It does *not* necessarily
      indicate that there will be application data returned from a call to
      SSL_read(). The unprocessed data may not be application data or there
      could be errors when we attempt to parse the records.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      Reviewed-by: NEmilia Käsper <emilia@openssl.org>
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      892b9376