1. 07 5月, 2016 1 次提交
  2. 06 5月, 2016 1 次提交
    • M
      Handle no async jobs in libssl · fc7f190c
      Matt Caswell 提交于
      If the application has limited the size of the async pool using
      ASYNC_init_thread() then we could run out of jobs while trying to start a
      libssl io operation. However libssl was failing to handle this and treating
      it like a fatal error. It should not be fatal...we just need to retry when
      there are jobs available again.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      fc7f190c
  3. 04 5月, 2016 1 次提交
  4. 03 5月, 2016 1 次提交
    • T
      Secure memory fixes · e8408681
      Todd Short 提交于
      Fix some of the variables to be (s)size_t, so that more than 1GB of
      secure memory can be allocated. The arena has to be a power of 2, and
      2GB fails because it ends up being a negative 32-bit signed number.
      
      The |too_late| flag is not strictly necessary; it is easy to figure
      out if something is secure memory by looking at the arena. As before,
      secure memory allocations will not fail, but now they can be freed
      correctly. Once initialized, secure memory can still be used, even if
      allocations occured before initialization.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      e8408681
  5. 30 4月, 2016 5 次提交
  6. 29 4月, 2016 7 次提交
  7. 27 4月, 2016 1 次提交
  8. 26 4月, 2016 1 次提交
  9. 25 4月, 2016 1 次提交
  10. 22 4月, 2016 6 次提交
  11. 20 4月, 2016 5 次提交
  12. 19 4月, 2016 2 次提交
  13. 18 4月, 2016 4 次提交
  14. 17 4月, 2016 1 次提交
  15. 16 4月, 2016 1 次提交
  16. 15 4月, 2016 1 次提交
    • M
      Fix ex_data locks issue · 1ee7b8b9
      Matt Caswell 提交于
      Travis identified a problem with freeing the ex_data locks which wasn't
      quite right in ff234405. Trying to fix it identified a further problem:
      the ex_data locks are cleaned up by OPENSSL_cleanup(), which is called
      explicitly by CRYPTO_mem_leaks(), but then later the BIO passed to
      CRYPTO_mem_leaks() is freed. An attempt is then made to use the ex_data
      lock already freed.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      1ee7b8b9
  17. 14 4月, 2016 1 次提交