1. 20 3月, 2018 1 次提交
  2. 12 3月, 2018 1 次提交
  3. 13 11月, 2017 1 次提交
  4. 06 11月, 2017 1 次提交
  5. 07 7月, 2017 1 次提交
  6. 21 6月, 2017 1 次提交
  7. 13 4月, 2017 1 次提交
  8. 10 4月, 2017 1 次提交
  9. 04 4月, 2017 1 次提交
  10. 03 3月, 2017 2 次提交
  11. 22 2月, 2017 1 次提交
  12. 30 1月, 2017 3 次提交
  13. 10 1月, 2017 1 次提交
  14. 04 11月, 2016 2 次提交
  15. 18 8月, 2016 1 次提交
  16. 18 5月, 2016 1 次提交
  17. 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
  18. 17 12月, 2015 1 次提交
    • R
      Rename some BUF_xxx to OPENSSL_xxx · 7644a9ae
      Rich Salz 提交于
      Rename BUF_{strdup,strlcat,strlcpy,memdup,strndup,strnlen}
      to OPENSSL_{strdup,strlcat,strlcpy,memdup,strndup,strnlen}
      Add #define's for the old names.
      Add CRYPTO_{memdup,strndup}, called by OPENSSL_{memdup,strndup} macros.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      7644a9ae
  19. 11 9月, 2015 1 次提交
  20. 23 5月, 2015 1 次提交
  21. 13 5月, 2015 1 次提交
  22. 05 5月, 2015 1 次提交
  23. 02 5月, 2015 1 次提交
  24. 01 5月, 2015 1 次提交
  25. 11 4月, 2015 1 次提交
  26. 03 4月, 2015 1 次提交
  27. 28 2月, 2015 1 次提交
    • M
      Fix d2i_SSL_SESSION for DTLS1_BAD_VER · af674d4e
      Matt Caswell 提交于
      Some Cisco appliances use a pre-standard version number for DTLS. We support
      this as DTLS1_BAD_VER within the code.
      
      This change fixes d2i_SSL_SESSION for that DTLS version.
      
      Based on an original patch by David Woodhouse <dwmw2@infradead.org>
      
      RT#3704
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      af674d4e
  28. 11 2月, 2015 1 次提交
    • M
      Correct reading back of tlsext_tick_lifetime_hint from ASN1. · ea6bd264
      Matt Caswell 提交于
      When writing out the hint, if the hint > 0, then we write it out otherwise
      we skip it.
      
      Previously when reading the hint back in, if were expecting to see one
      (because the ticket length > 0), but it wasn't present then we set the hint
      to -1, otherwise we set it to 0. This fails to set the hint to the same as
      when it was written out.
      
      The hint should never be negative because the RFC states the hint is
      unsigned. It is valid for a server to set the hint to 0 (this means the
      lifetime is unspecified according to the RFC). If the server set it to 0, it
      should still be 0 when we read it back in.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      ea6bd264
  29. 03 2月, 2015 1 次提交
  30. 22 1月, 2015 1 次提交
  31. 04 12月, 2014 1 次提交
  32. 08 5月, 2014 1 次提交
  33. 04 6月, 2012 1 次提交
  34. 25 10月, 2011 1 次提交
  35. 05 9月, 2011 1 次提交
  36. 13 3月, 2011 1 次提交