1. 29 2月, 2016 1 次提交
  2. 24 2月, 2016 1 次提交
  3. 09 2月, 2016 1 次提交
  4. 06 2月, 2016 1 次提交
  5. 29 1月, 2016 1 次提交
  6. 28 1月, 2016 1 次提交
  7. 27 1月, 2016 1 次提交
    • R
      Remove /* foo.c */ comments · 34980760
      Rich Salz 提交于
      This was done by the following
              find . -name '*.[ch]' | /tmp/pl
      where /tmp/pl is the following three-line script:
              print unless $. == 1 && m@/\* .*\.[ch] \*/@;
              close ARGV if eof; # Close file to reset $.
      
      And then some hand-editing of other files.
      Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
      34980760
  8. 11 1月, 2016 1 次提交
  9. 08 1月, 2016 1 次提交
    • R
      mem functions cleanup · bbd86bf5
      Rich Salz 提交于
      Only two macros CRYPTO_MDEBUG and CRYPTO_MDEBUG_ABORT to control this.
      If CRYPTO_MDEBUG is not set, #ifdef out the whole debug machinery.
              (Thanks to Jakob Bohm for the suggestion!)
      Make the "change wrapper functions" be the only paradigm.
      Wrote documentation!
      Format the 'set func' functions so their paramlists are legible.
      Format some multi-line comments.
      Remove ability to get/set the "memory debug" functions at runtme.
      Remove MemCheck_* and CRYPTO_malloc_debug_init macros.
      Add CRYPTO_mem_debug(int flag) function.
      Add test/memleaktest.
      Rename CRYPTO_malloc_init to OPENSSL_malloc_init; remove needless calls.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      bbd86bf5
  10. 20 12月, 2015 1 次提交
  11. 10 6月, 2015 1 次提交
    • M
      EC_POINT_is_on_curve does not return a boolean · 68886be7
      Matt Caswell 提交于
      The function EC_POINT_is_on_curve does not return a boolean value.
      It returns 1 if the point is on the curve, 0 if it is not, and -1
      on error. Many usages within OpenSSL were incorrectly using this
      function and therefore not correctly handling error conditions.
      
      With thanks to the Open Crypto Audit Project for reporting this issue.
      Reviewed-by: NKurt Roeckx <kurt@openssl.org>
      68886be7
  12. 11 5月, 2015 1 次提交
  13. 05 5月, 2015 1 次提交
    • R
      Use safer sizeof variant in malloc · b4faea50
      Rich Salz 提交于
      For a local variable:
              TYPE *p;
      Allocations like this are "risky":
              p = OPENSSL_malloc(sizeof(TYPE));
      if the type of p changes, and the malloc call isn't updated, you
      could get memory corruption.  Instead do this:
              p = OPENSSL_malloc(sizeof(*p));
      Also fixed a few memset() calls that I noticed while doing this.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      b4faea50
  14. 04 5月, 2015 1 次提交
  15. 01 5月, 2015 1 次提交
    • R
      free NULL cleanup 7 · 23a1d5e9
      Rich Salz 提交于
      This gets BN_.*free:
          BN_BLINDING_free BN_CTX_free BN_FLG_FREE BN_GENCB_free
          BN_MONT_CTX_free BN_RECP_CTX_free BN_clear_free BN_free BUF_MEM_free
      
      Also fix a call to DSA_SIG_free to ccgost engine and remove some #ifdef'd
      dead code in engines/e_ubsec.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      23a1d5e9
  16. 01 4月, 2015 1 次提交
  17. 26 3月, 2015 1 次提交
  18. 06 2月, 2015 1 次提交
  19. 03 2月, 2015 1 次提交
  20. 22 1月, 2015 2 次提交
  21. 20 12月, 2014 1 次提交
  22. 17 12月, 2014 1 次提交
    • E
      Build fixes · b597aab8
      Emilia Kasper 提交于
      Various build fixes, mostly uncovered by clang's unused-const-variable
      and unused-function errors.
      Reviewed-by: NKurt Roeckx <kurt@openssl.org>
      (cherry picked from commit 0e1c318ece3c82e96ae95a34a1badf58198d6b28)
      b597aab8
  23. 09 12月, 2014 1 次提交
  24. 13 8月, 2014 1 次提交
  25. 01 8月, 2014 1 次提交
  26. 19 10月, 2011 2 次提交
  27. 13 2月, 2011 1 次提交
  28. 10 1月, 2011 1 次提交
  29. 06 9月, 2010 1 次提交
  30. 27 8月, 2010 1 次提交
  31. 26 8月, 2010 1 次提交
  32. 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
  33. 04 7月, 2008 1 次提交
  34. 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
  35. 22 5月, 2007 1 次提交
  36. 29 8月, 2005 1 次提交
  37. 11 8月, 2005 1 次提交
  38. 08 8月, 2005 1 次提交