1. 19 4月, 2017 1 次提交
  2. 16 6月, 2016 1 次提交
  3. 06 6月, 2016 1 次提交
  4. 18 5月, 2016 1 次提交
  5. 03 4月, 2016 2 次提交
  6. 18 3月, 2016 1 次提交
  7. 09 2月, 2016 1 次提交
  8. 06 2月, 2016 1 次提交
  9. 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
  10. 23 1月, 2016 1 次提交
  11. 11 1月, 2016 1 次提交
  12. 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
  13. 06 9月, 2015 1 次提交
  14. 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
  15. 01 4月, 2015 1 次提交
  16. 25 3月, 2015 2 次提交
  17. 29 1月, 2015 1 次提交
  18. 22 1月, 2015 1 次提交
  19. 13 1月, 2015 1 次提交
  20. 19 12月, 2014 1 次提交
  21. 09 12月, 2014 1 次提交
  22. 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
  23. 04 7月, 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. 16 3月, 2006 1 次提交
  26. 16 7月, 2005 1 次提交
    • N
      make · 3eeaab4b
      Nils Larsch 提交于
          	./configure no-deprecated [no-dsa] [no-dh] [no-ec] [no-rsa]
          	make depend all test
      work again
      
      PR: 1159
      3eeaab4b
  27. 16 5月, 2005 1 次提交
    • B
      Implement fixed-window exponentiation to mitigate hyper-threading · 46a64376
      Bodo Möller 提交于
      timing attacks.
      
      BN_FLG_EXP_CONSTTIME requests this algorithm, and this done by default for
      RSA/DSA/DH private key computations unless
      RSA_FLAG_NO_EXP_CONSTTIME/DSA_FLAG_NO_EXP_CONSTTIME/
      DH_FLAG_NO_EXP_CONSTTIME is set.
      
      Submitted by: Matthew D Wood
      Reviewed by: Bodo Moeller
      46a64376
  28. 28 11月, 2003 1 次提交
  29. 29 10月, 2003 1 次提交
  30. 08 4月, 2003 1 次提交
  31. 04 4月, 2003 1 次提交
  32. 21 3月, 2003 1 次提交
  33. 23 2月, 2003 1 次提交
  34. 31 1月, 2003 1 次提交
  35. 08 12月, 2002 1 次提交
    • G
      This is a first-cut at improving the callback mechanisms used in · e9224c71
      Geoff Thorpe 提交于
      key-generation and prime-checking functions. Rather than explicitly passing
      callback functions and caller-defined context data for the callbacks, a new
      structure BN_GENCB is defined that encapsulates this; a pointer to the
      structure is passed to all such functions instead.
      
      This wrapper structure allows the encapsulation of "old" and "new" style
      callbacks - "new" callbacks return a boolean result on the understanding
      that returning FALSE should terminate keygen/primality processing.  The
      BN_GENCB abstraction will allow future callback modifications without
      needing to break binary compatibility nor change the API function
      prototypes. The new API functions have been given names ending in "_ex" and
      the old functions are implemented as wrappers to the new ones.  The
      OPENSSL_NO_DEPRECATED symbol has been introduced so that, if defined,
      declaration of the older functions will be skipped. NB: Some
      openssl-internal code will stick with the older callbacks for now, so
      appropriate "#undef" logic will be put in place - this is in case the user
      is *building* openssl (rather than *including* its headers) with this
      symbol defined.
      
      There is another change in the new _ex functions; the key-generation
      functions do not return key structures but operate on structures passed by
      the caller, the return value is a boolean. This will allow for a smoother
      transition to having key-generation as "virtual function" in the various
      ***_METHOD tables.
      e9224c71
  36. 06 12月, 2002 1 次提交
  37. 01 12月, 2002 1 次提交
  38. 29 11月, 2002 1 次提交