1. 20 3月, 2018 1 次提交
  2. 19 3月, 2018 1 次提交
  3. 07 8月, 2017 1 次提交
  4. 13 1月, 2017 1 次提交
    • R
      Add "random malloc failure" tooling · f7edeced
      Rich Salz 提交于
      Still needs to be documented, somehow/somewhere.
      
      The env var OPENSSL_MALLOC_FAILURES controls how often malloc/realloc
      should fail.  It's a set of fields separated by semicolons.  Each field
      is a count and optional percentage (separated by @) which defaults to 100.
      If count is zero then it lasts "forever."  For example: 100;@25 means the
      first 100 allocations pass, then the rest have a 25% chance of failing
      until the program exits or crashes.
      
      If env var OPENSSL_MALLOC_FD parses as a positive integer, a record
      of all malloc "shouldfail" tests is written to that file descriptor.
      If a malloc will fail, and OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE is not set
      (platform specific), then a backtrace will be written to the descriptor
      when a malloc fails.  This can be useful because a malloc may fail but
      not be checked, and problems will only occur later.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/1252)
      f7edeced
  5. 06 8月, 2016 1 次提交
  6. 18 5月, 2016 1 次提交
  7. 29 4月, 2016 1 次提交
  8. 15 4月, 2016 1 次提交
    • M
      Fix ex_data locks issue · 1ee7b8b9
      Matt Caswell 提交于
      Travis identified a problem with freeing the ex_data locks which wasn't
      quite right in ff234405. Trying to fix it identified a further problem:
      the ex_data locks are cleaned up by OPENSSL_cleanup(), which is called
      explicitly by CRYPTO_mem_leaks(), but then later the BIO passed to
      CRYPTO_mem_leaks() is freed. An attempt is then made to use the ex_data
      lock already freed.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      1ee7b8b9
  9. 14 4月, 2016 1 次提交
  10. 05 4月, 2016 2 次提交
  11. 07 3月, 2016 1 次提交
  12. 10 2月, 2016 1 次提交
  13. 09 2月, 2016 2 次提交
  14. 26 1月, 2016 1 次提交
    • R
      Generate warning text · 9ab6fc59
      Richard Levitte 提交于
      Now that we're using templates, we should warn people not to edit the
      resulting file.  We do it through util/dofile.pl, which is enhanced
      with an option to tell what file it was called from.  We also change
      the calls so the template files are on the command line instead of
      being redirected through standard input.  That way, we can display
      something like this (example taken from include/openssl/opensslconf.h):
      
          /* WARNING: do not edit! */
          /* Generated by Configure from include/openssl/opensslconf.h.in */
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      9ab6fc59
  15. 25 1月, 2016 1 次提交
  16. 05 9月, 2015 1 次提交
  17. 17 9月, 2006 1 次提交
  18. 04 6月, 1999 1 次提交
  19. 30 1月, 1999 1 次提交
  20. 24 1月, 1999 1 次提交
  21. 17 1月, 1999 1 次提交
    • D
      Time to blow up the source tree :-) This is the beginning of support for · f6aed2cd
      Dr. Stephen Henson 提交于
      GeneralizedTime. At several points PKIX specifies that GeneralizedTime can be
      used but OpenSSL doesn't currently support it. This patch adds several files
      and a bunch of functions.
      
      Of interest is the ASN1_TIME structure and its related functions. At several
      points certificates, CRLs et al specify that a time can be expressed as a
      choice of UTCTime and GeneralizedTime. Currently OpenSSL interprets this
      (wrongly) as UTCTime because GeneralizedTime isn't supported. The ASN1_TIME
      stuff provides this functionality.
      
      Still todo is to trace which cert and CRL points need an ASN1_TIME and modify
      the utilities appropriately and of course fix all the bugs.
      
      Note new OpenSSL copyright in the new file a_time.c. I didn't put it in
      a_gentm.c because it is a minimally modified form a_utctm.c .
      
      Since this adds new files and error codes you will need to do a 'make errors'
      at the top level to add the new codes.
      f6aed2cd