1. 27 1月, 2011 2 次提交
  2. 26 1月, 2011 2 次提交
  3. 12 10月, 2010 1 次提交
    • D
      PR: 2295 · 776654ad
      Dr. Stephen Henson 提交于
      Submitted by: Alexei Khlebnikov <alexei.khlebnikov@opera.com>
      Reviewed by: steve
      
      OOM checking. Leak in OOM fix. Fall-through comment. Duplicate code
      elimination.
      776654ad
  4. 04 10月, 2010 1 次提交
  5. 10 8月, 2010 1 次提交
  6. 01 6月, 2010 1 次提交
  7. 12 3月, 2010 2 次提交
  8. 11 3月, 2010 5 次提交
  9. 09 3月, 2010 1 次提交
  10. 08 3月, 2010 1 次提交
  11. 07 3月, 2010 4 次提交
  12. 09 12月, 2009 1 次提交
    • D
      PR: 2124 · fdb2c6e4
      Dr. Stephen Henson 提交于
      Submitted by: Jan Pechanec <Jan.Pechanec@Sun.COM>
      
      Check for memory allocation failures.
      fdb2c6e4
  13. 24 9月, 2009 1 次提交
  14. 13 9月, 2009 1 次提交
  15. 05 8月, 2009 1 次提交
  16. 27 6月, 2009 1 次提交
  17. 30 12月, 2008 1 次提交
  18. 29 12月, 2008 1 次提交
  19. 12 11月, 2008 1 次提交
  20. 06 11月, 2008 1 次提交
  21. 02 11月, 2008 1 次提交
  22. 14 9月, 2008 1 次提交
  23. 06 8月, 2008 1 次提交
    • G
      Remove the dual-callback scheme for numeric and pointer thread IDs, · 4c329696
      Geoff Thorpe 提交于
      deprecate the original (numeric-only) scheme, and replace with the
      CRYPTO_THREADID object. This hides the platform-specifics and should reduce
      the possibility for programming errors (where failing to explicitly check
      both thread ID forms could create subtle, platform-specific bugs).
      
      Thanks to Bodo, for invaluable review and feedback.
      4c329696
  24. 18 7月, 2008 1 次提交
  25. 04 7月, 2008 1 次提交
  26. 22 6月, 2008 1 次提交
  27. 04 6月, 2008 1 次提交
  28. 20 5月, 2008 1 次提交
  29. 02 5月, 2008 1 次提交
  30. 28 3月, 2008 1 次提交
    • G
      There was a need to support thread ID types that couldn't be reliably cast · f7ccba3e
      Geoff Thorpe 提交于
      to 'unsigned long' (ie. odd platforms/compilers), so a pointer-typed
      version was added but it required portable code to check *both* modes to
      determine equality. This commit maintains the availability of both thread
      ID types, but deprecates the type-specific accessor APIs that invoke the
      callbacks - instead a single type-independent API is used.  This simplifies
      software that calls into this interface, and should also make it less
      error-prone - as forgetting to call and compare *both* thread ID accessors
      could have led to hard-to-debug/infrequent bugs (that might only affect
      certain platforms or thread implementations). As the CHANGES note says,
      there were corresponding deprecations and replacements in the
      thread-related functions for BN_BLINDING and ERR too.
      f7ccba3e