1. 01 5月, 2015 1 次提交
    • R
      free cleanup almost the finale · 4b45c6e5
      Rich Salz 提交于
      Add OPENSSL_clear_free which merges cleanse and free.
      (Names was picked to be similar to BN_clear_free, etc.)
      Removed OPENSSL_freeFunc macro.
      Fixed the small simple ones that are left:
              CRYPTO_free CRYPTO_free_locked OPENSSL_free_locked
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      4b45c6e5
  2. 17 4月, 2015 1 次提交
  3. 01 4月, 2015 2 次提交
  4. 25 3月, 2015 2 次提交
    • 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
    • M
      RAND_bytes updates · 266483d2
      Matt Caswell 提交于
      Ensure RAND_bytes return value is checked correctly, and that we no longer
      use RAND_pseudo_bytes.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      266483d2
  5. 05 3月, 2015 1 次提交
  6. 13 2月, 2015 1 次提交
  7. 06 2月, 2015 1 次提交
  8. 30 1月, 2015 1 次提交
  9. 29 1月, 2015 1 次提交
  10. 28 1月, 2015 1 次提交
    • R
      OPENSSL_NO_xxx cleanup: SHA · 474e469b
      Rich Salz 提交于
      Remove support for SHA0 and DSS0 (they were broken), and remove
      the ability to attempt to build without SHA (it didn't work).
      For simplicity, remove the option of not building various SHA algorithms;
      you could argue that SHA_224/256/384/512 should be kept, since they're
      like crypto algorithms, but I decided to go the other way.
      So these options are gone:
      	GENUINE_DSA         OPENSSL_NO_SHA0
      	OPENSSL_NO_SHA      OPENSSL_NO_SHA1
      	OPENSSL_NO_SHA224   OPENSSL_NO_SHA256
      	OPENSSL_NO_SHA384   OPENSSL_NO_SHA512
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      474e469b
  11. 24 1月, 2015 2 次提交
  12. 23 1月, 2015 1 次提交
  13. 22 1月, 2015 5 次提交
  14. 13 1月, 2015 1 次提交
  15. 06 1月, 2015 1 次提交
  16. 31 12月, 2014 1 次提交
  17. 18 12月, 2014 2 次提交
  18. 08 12月, 2014 3 次提交
  19. 29 11月, 2014 1 次提交
  20. 25 9月, 2014 1 次提交
  21. 19 9月, 2014 1 次提交
  22. 09 6月, 2014 1 次提交
    • J
      Create ~/.rnd with mode 0600 instead of 0666 · 7be1d876
      Jakub Wilk 提交于
      Because of a missing include <fcntl.h> we don't have O_CREATE and don't create
      the file with open() using mode 0600 but fall back to using fopen() with the
      default umask followed by a chmod().
      
      Problem found by Jakub Wilk <jwilk@debian.org>.
      7be1d876
  23. 09 4月, 2014 1 次提交
  24. 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
  25. 25 2月, 2014 1 次提交
    • D
      Avoid Windows 8 Getversion deprecated errors. · a4cc3c80
      Dr. Stephen Henson 提交于
      Windows 8 SDKs complain that GetVersion() is deprecated.
      
      We only use GetVersion like this:
      
      	(GetVersion() < 0x80000000)
      
      which checks if the Windows version is NT based. Use a macro check_winnt()
      which uses GetVersion() on older SDK versions and true otherwise.
      a4cc3c80
  26. 12 1月, 2014 1 次提交
  27. 11 1月, 2014 1 次提交
  28. 21 10月, 2013 1 次提交
  29. 20 9月, 2013 1 次提交
  30. 06 9月, 2013 1 次提交