1. 27 7月, 2017 1 次提交
  2. 19 7月, 2017 1 次提交
  3. 15 7月, 2017 1 次提交
    • R
      Start to overhaul RAND API · da8fc25a
      Rich Salz 提交于
      Remove unused rand_hw_xor, MD/EVP indirection
      Make rand_pseudo same as rand.
      Cleanup formatting and ifdef control
      Rename some things:
          - rand_meth to openssl_rand_meth; make it global
          - source file
          - lock/init functions, start per-thread state
          - ossl_meth_init to ossl_rand_init
      Put state into RAND_STATE structure
      And put OSSL_RAND_STATE into ossl_typ.h
      Use "randomness" instead of "entropy"
      Reviewed-by: NBen Kaduk <kaduk@mit.edu>
      (Merged from https://github.com/openssl/openssl/pull/3758)
      da8fc25a
  4. 28 2月, 2017 1 次提交
    • E
      Clean up references to FIPS · b53338cb
      Emilia Kasper 提交于
      This removes the fips configure option. This option is broken as the
      required FIPS code is not available.
      
      FIPS_mode() and FIPS_mode_set() are retained for compatibility, but
      FIPS_mode() always returns 0, and FIPS_mode_set() can only be used to
      turn FIPS mode off.
      Reviewed-by: NStephen Henson <steve@openssl.org>
      b53338cb
  5. 07 1月, 2017 1 次提交
  6. 09 12月, 2016 1 次提交
  7. 03 12月, 2016 1 次提交
  8. 08 9月, 2016 1 次提交
    • M
      Fix mem leaks during auto-deinit · 135648bc
      Matt Caswell 提交于
      Certain functions are automatically called during auto-deinit in order
      to deallocate resources. However, if we have never entered a function which
      marks lib crypto as inited then they never get called. This can happen if
      the user only ever makes use of a small sub-set of functions that don't hit
      the auto-init code.
      
      This commit ensures all such resources deallocated by these functions also
      init libcrypto when they are initially allocated.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      Reviewed-by: NBen Laurie <ben@openssl.org>
      135648bc
  9. 20 7月, 2016 1 次提交
  10. 16 7月, 2016 1 次提交
  11. 15 7月, 2016 1 次提交
  12. 01 6月, 2016 1 次提交
  13. 18 5月, 2016 1 次提交
  14. 17 5月, 2016 1 次提交
  15. 09 3月, 2016 1 次提交
  16. 19 2月, 2016 1 次提交
    • R
      Remove outdated DEBUG flags. · d63a5e5e
      Rich Salz 提交于
      Add -DBIO_DEBUG to --strict-warnings.
      Remove comments about outdated debugging ifdef guards.
      Remove md_rand ifdef guarding an assert; it doesn't seem used.
      Remove the conf guards in conf_api since we use OPENSSL_assert, not assert.
      For pkcs12 stuff put OPENSSL_ in front of the macro name.
      Merge TLS_DEBUG into SSL_DEBUG.
      Various things just turned on/off asserts, mainly for checking non-NULL
      arguments, which is now removed: camellia, bn_ctx, crypto/modes.
      Remove some old debug code, that basically just printed things to stderr:
        DEBUG_PRINT_UNKNOWN_CIPHERSUITES, DEBUG_ZLIB, OPENSSL_RI_DEBUG,
        RL_DEBUG, RSA_DEBUG, SCRYPT_DEBUG.
      Remove OPENSSL_SSL_DEBUG_BROKEN_PROTOCOL.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      d63a5e5e
  17. 17 2月, 2016 1 次提交
  18. 06 2月, 2016 1 次提交
  19. 05 2月, 2016 1 次提交
  20. 29 1月, 2016 1 次提交
  21. 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
  22. 08 1月, 2016 1 次提交
  23. 08 12月, 2015 2 次提交
  24. 21 11月, 2015 1 次提交
    • M
      Fix async deadlock problem · 625146d9
      Matt Caswell 提交于
      The rand code can aquire locks and then attempt crypto operations. This
      can end up in a deadlock if we are using an async engine, because control
      returns back to the user code whilst still holding the lock. We need to
      force synchronous operation for these sections of code.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      625146d9
  25. 31 10月, 2015 1 次提交
  26. 11 8月, 2015 1 次提交
  27. 25 3月, 2015 1 次提交
    • M
      Deprecate RAND_pseudo_bytes · 302d38e3
      Matt Caswell 提交于
      The justification for RAND_pseudo_bytes is somewhat dubious, and the reality
      is that it is frequently being misused. RAND_bytes and RAND_pseudo_bytes in
      the default implementation both end up calling ssleay_rand_bytes. Both may
      return -1 in an error condition. If there is insufficient entropy then
      both will return 0, but RAND_bytes will additionally add an error to the
      error queue. They both return 1 on success.
      Therefore the fundamental difference between the two is that one will add an
      error to the error queue with insufficient entory whilst the other will not.
      Frequently there are constructions of this form:
      
      if(RAND_pseudo_bytes(...) <= 1)
      	goto err;
      
      In the above form insufficient entropy is treated as an error anyway, so
      RAND_bytes is probably the better form to use.
      
      This form is also seen:
      if(!RAND_pseudo_bytes(...))
      	goto err;
      
      This is technically not correct at all since a -1 return value is
      incorrectly handled - but this form will also treat insufficient entropy as
      an error.
      
      Within libssl it is required that you have correctly seeded your entropy
      pool and so there seems little benefit in using RAND_pseudo_bytes.
      Similarly in libcrypto many operations also require a correctly seeded
      entropy pool and so in most interesting cases you would be better off
      using RAND_bytes anyway. There is a significant risk of RAND_pseudo_bytes
      being incorrectly used in scenarios where security can be compromised by
      insufficient entropy.
      
      If you are not using the default implementation, then most engines use the
      same function to implement RAND_bytes and RAND_pseudo_bytes in any case.
      
      Given its misuse, limited benefit, and potential to compromise security,
      RAND_pseudo_bytes has been deprecated.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      302d38e3
  28. 24 1月, 2015 1 次提交
  29. 22 1月, 2015 2 次提交
  30. 08 12月, 2014 1 次提交
  31. 09 4月, 2014 1 次提交
  32. 08 4月, 2014 1 次提交
    • D
      Return if ssleay_rand_add called with zero num. · f74fa33b
      Dr. Stephen Henson 提交于
      Treat a zero length passed to ssleay_rand_add a no op: the existing logic
      zeroes the md value which is very bad. OpenSSL itself never does this
      internally and the actual call doesn't make sense as it would be passing
      zero bytes of entropy.
      
      Thanks to Marcus Meissner <meissner@suse.de> for reporting this bug.
      (cherry picked from commit 5be1ae28ef3c4bdec95b94f14e0e939157be550a)
      f74fa33b
  33. 12 1月, 2014 1 次提交
  34. 11 1月, 2014 1 次提交
  35. 21 10月, 2013 1 次提交
  36. 20 9月, 2013 1 次提交
  37. 16 2月, 2011 1 次提交
  38. 27 1月, 2011 1 次提交