1. 08 4月, 2009 1 次提交
  2. 03 4月, 2009 1 次提交
  3. 13 3月, 2009 1 次提交
  4. 08 3月, 2009 1 次提交
  5. 15 2月, 2009 1 次提交
    • D
      PR: 1835 · 477fd459
      Dr. Stephen Henson 提交于
      Submitted by: Damien Miller <djm@mindrot.org>
      Approved by: steve@openssl.org
      
      Fix various typos.
      477fd459
  6. 02 2月, 2009 1 次提交
  7. 10 11月, 2008 1 次提交
  8. 03 11月, 2008 1 次提交
  9. 07 8月, 2008 1 次提交
  10. 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
  11. 01 8月, 2008 1 次提交
  12. 13 7月, 2008 1 次提交
    • D
      X509 verification fixes. · db50661f
      Dr. Stephen Henson 提交于
      Ignore self issued certificates when checking path length constraints.
      
      Duplicate OIDs in policy tree in case they are allocated.
      
      Use anyPolicy from certificate cache and not current tree level.
      db50661f
  13. 04 7月, 2008 1 次提交
  14. 03 6月, 2008 1 次提交
  15. 26 5月, 2008 1 次提交
  16. 19 5月, 2008 2 次提交
  17. 03 5月, 2008 1 次提交
  18. 02 5月, 2008 2 次提交
  19. 12 4月, 2008 3 次提交
  20. 11 4月, 2008 1 次提交
  21. 10 4月, 2008 10 次提交
  22. 09 4月, 2008 3 次提交
  23. 29 3月, 2008 1 次提交
  24. 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
  25. 21 3月, 2008 1 次提交