1. 28 3月, 2014 1 次提交
  2. 21 1月, 2007 1 次提交
  3. 31 1月, 2003 1 次提交
  4. 17 3月, 2002 1 次提交
    • D
      · 3e268d27
      Dr. Stephen Henson 提交于
      Ensure EVP_CipherInit() uses the correct encode/decode parameter if
      enc == -1
      
      [Reported by Markus Friedl <markus@openbsd.org>]
      
      Fix typo in dh_lib.c (use of DSAerr instead of DHerr).
      3e268d27
  5. 10 3月, 2002 1 次提交
    • D
      · 0c372b94
      Dr. Stephen Henson 提交于
      Make {RSA,DSA,DH}_new_method obtain and release an ENGINE
      functional reference in all cases.
      0c372b94
  6. 26 9月, 2001 2 次提交
    • G
      indentation. · 50a381b7
      Geoff Thorpe 提交于
      50a381b7
    • G
      This commits changes to various parts of libcrypto required by the recent · cb78486d
      Geoff Thorpe 提交于
      ENGINE surgery. DH, DSA, RAND, and RSA now use *both* "method" and ENGINE
      pointers to manage their hooking with ENGINE. Previously their use of
      "method" pointers was replaced by use of ENGINE references. See
      crypto/engine/README for details.
      
      Also, remove the ENGINE iterations from evp_test - even when the
      cipher/digest code is committed in, this functionality would require a
      different set of API calls.
      cb78486d
  7. 06 9月, 2001 1 次提交
  8. 02 9月, 2001 1 次提交
    • G
      Make the necessary changes to work with the recent "ex_data" overhaul. · 79aa04ef
      Geoff Thorpe 提交于
      See the commit log message for that for more information.
      
      NB: X509_STORE_CTX's use of "ex_data" support was actually misimplemented
      (initialisation by "memset" won't/can't/doesn't work). This fixes that but
      requires that X509_STORE_CTX_init() be able to handle errors - so its
      prototype has been changed to return 'int' rather than 'void'. All uses of
      that function throughout the source code have been tracked down and
      adjusted.
      79aa04ef
  9. 26 8月, 2001 1 次提交
  10. 13 8月, 2001 1 次提交
    • G
      The indexes returned by ***_get_ex_new_index() functions are used when · b7727ee6
      Geoff Thorpe 提交于
      setting stack (actually, array) values in ex_data. So only increment the
      global counters if the underlying CRYPTO_get_ex_new_index() call succeeds.
      This change doesn't make "ex_data" right (see the comment at the head of
      ex_data.c to know why), but at least makes the source code marginally less
      frustrating.
      b7727ee6
  11. 27 7月, 2001 1 次提交
  12. 24 6月, 2001 1 次提交
  13. 30 4月, 2001 1 次提交
  14. 30 11月, 2000 1 次提交
  15. 07 11月, 2000 1 次提交
  16. 27 10月, 2000 1 次提交
  17. 02 6月, 2000 1 次提交
    • R
      There have been a number of complaints from a number of sources that names · 26a3a48d
      Richard Levitte 提交于
      like Malloc, Realloc and especially Free conflict with already existing names
      on some operating systems or other packages.  That is reason enough to change
      the names of the OpenSSL memory allocation macros to something that has a
      better chance of being unique, like prepending them with OPENSSL_.
      
      This change includes all the name changes needed throughout all C files.
      26a3a48d
  18. 20 4月, 2000 1 次提交
  19. 28 1月, 2000 1 次提交
    • D
      · 90644dd7
      Dr. Stephen Henson 提交于
      New -pkcs12 option to CA.pl.
      Document CA.pl script.
      Initialise and free up the extra DH fields
      (nothing uses them yet though).
      90644dd7
  20. 24 1月, 2000 1 次提交
    • D
      · dd9d233e
      Dr. Stephen Henson 提交于
      Tidy up CRYPTO_EX_DATA structures.
      dd9d233e
  21. 02 9月, 1999 1 次提交
  22. 24 8月, 1999 1 次提交
  23. 24 4月, 1999 1 次提交
  24. 20 4月, 1999 1 次提交
  25. 18 4月, 1999 1 次提交
  26. 22 3月, 1999 1 次提交
  27. 06 1月, 1999 1 次提交
  28. 31 12月, 1998 1 次提交
    • R
      Fix version stuff: · 9cb0969f
      Ralf S. Engelschall 提交于
      1. The already released version was 0.9.1c and not 0.9.1b
      
      2. The next release should be 0.9.2 and not 0.9.1d, because
         first the changes are already too large, second we should avoid any more
         0.9.1x confusions and third, the Apache version semantics of
         VERSION.REVISION.PATCHLEVEL for the version string is reasonable (and here
         .2 is already just a patchlevel and not major change).
      tVS: ----------------------------------------------------------------------
      9cb0969f
  29. 23 12月, 1998 2 次提交
  30. 22 12月, 1998 1 次提交
  31. 21 12月, 1998 3 次提交