1. 09 7月, 2019 1 次提交
  2. 06 6月, 2019 1 次提交
  3. 04 6月, 2019 1 次提交
    • S
      Move digests to providers · d5e5e2ff
      Shane Lontis 提交于
      Move digest code into the relevant providers (fips, default, legacy).
      The headers are temporarily moved to be internal, and will be moved
      into providers after all external references are resolved. The deprecated
      digest code can not be removed until EVP_PKEY (signing) is supported by
      providers. EVP_MD data can also not yet be cleaned up for the same reasons.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/8763)
      d5e5e2ff
  4. 16 5月, 2019 1 次提交
  5. 03 5月, 2019 1 次提交
  6. 19 4月, 2019 2 次提交
  7. 03 4月, 2019 1 次提交
  8. 21 3月, 2019 2 次提交
  9. 19 3月, 2019 1 次提交
  10. 07 3月, 2019 1 次提交
  11. 27 2月, 2019 1 次提交
  12. 13 2月, 2019 1 次提交
  13. 06 2月, 2019 2 次提交
  14. 06 12月, 2018 1 次提交
  15. 14 11月, 2018 1 次提交
  16. 05 11月, 2018 2 次提交
  17. 30 10月, 2018 3 次提交
  18. 29 10月, 2018 2 次提交
  19. 07 9月, 2018 2 次提交
  20. 19 6月, 2018 1 次提交
  21. 13 4月, 2018 2 次提交
    • M
      Add support for the SRP base64 alphabet · 3fd59700
      Matt Caswell 提交于
      Historically we used to implement standalone base64 code for SRP. This
      was replaced by commit 3d3f21aa with the standard base64 processing code.
      
      However, the SRP base64 code was designed to be compatible with other SRP
      libraries (notably libsrp, but also others) that use a variant of standard
      base64. Specifically a different alphabet is used and no padding '='
      characters are used. Instead 0 padding is added to the front of the string.
      By changing to standard base64 we change the behaviour of the API which may
      impact interoperability. It also means that SRP verifier files created prior
      to 1.1.1 would not be readable in 1.1.1 and vice versa.
      
      Instead we expand our standard base64 processing with the capability to be
      able to read and generate the SRP base64 variant.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5925)
      3fd59700
    • M
      Change SRP functions to use EVP_EncodeUpdate/EVP_DecodeUpdate functions · c0804614
      Matt Caswell 提交于
      Previously they were using EVP_EncodeBlock/EVP_DecodeBlock. These are low
      level functions that do not handle padding characters. This was causing
      the SRP code to fail. One side effect of using EVP_EncodeUpdate is that
      it inserts newlines which is not what we need in SRP so we add a flag to
      avoid that.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5925)
      c0804614
  22. 02 3月, 2018 1 次提交
  23. 27 2月, 2018 1 次提交
  24. 23 2月, 2018 1 次提交
  25. 20 11月, 2017 1 次提交
  26. 12 11月, 2017 1 次提交
  27. 12 10月, 2017 1 次提交
  28. 14 9月, 2017 2 次提交
  29. 08 8月, 2017 1 次提交
  30. 31 5月, 2017 1 次提交