1. 19 10月, 2018 1 次提交
  2. 03 8月, 2017 1 次提交
  3. 31 7月, 2017 1 次提交
  4. 22 5月, 2017 2 次提交
  5. 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
  6. 04 11月, 2016 3 次提交
  7. 18 8月, 2016 1 次提交
  8. 15 7月, 2016 1 次提交
  9. 18 5月, 2016 1 次提交
  10. 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
  11. 08 12月, 2015 2 次提交
  12. 21 11月, 2015 1 次提交
  13. 20 11月, 2015 1 次提交
  14. 14 5月, 2015 1 次提交
  15. 01 5月, 2015 1 次提交
    • M
      Add sanity check in ssl3_cbc_digest_record · 29b0a15a
      Matt Caswell 提交于
      For SSLv3 the code assumes that |header_length| > |md_block_size|. Whilst
      this is true for all SSLv3 ciphersuites, this fact is far from obvious by
      looking at the code. If this were not the case then an integer overflow
      would occur, leading to a subsequent buffer overflow. Therefore I have
      added an explicit sanity check to ensure header_length is always valid.
      Thanks to Kevin Wojtysiak (Int3 Solutions) and Paramjot Oberoi (Int3
      Solutions) for reporting this issue.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      29b0a15a
  16. 26 3月, 2015 1 次提交
  17. 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
  18. 22 1月, 2015 3 次提交
  19. 06 1月, 2015 1 次提交
  20. 31 12月, 2014 1 次提交
  21. 08 12月, 2014 1 次提交
  22. 24 9月, 2014 1 次提交
  23. 28 8月, 2014 1 次提交
  24. 06 9月, 2013 1 次提交
  25. 18 3月, 2013 1 次提交
  26. 22 2月, 2013 1 次提交
  27. 12 2月, 2013 1 次提交
  28. 09 2月, 2013 1 次提交
  29. 08 2月, 2013 3 次提交
  30. 07 2月, 2013 1 次提交
    • A
      Fix for EXP-RC2-CBC-MD5 · 32620fe9
      Adam Langley 提交于
      MD5 should use little endian order. Fortunately the only ciphersuite
      affected is EXP-RC2-CBC-MD5 (TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5) which
      is a rarely used export grade ciphersuite.
      (cherry picked from commit f306b87d766e6ecf30824635c7c395b67cff9dbc)
      32620fe9
  31. 06 2月, 2013 2 次提交