1. 13 3月, 2018 1 次提交
  2. 22 8月, 2017 1 次提交
  3. 25 4月, 2017 1 次提交
  4. 22 2月, 2017 1 次提交
  5. 14 9月, 2016 1 次提交
    • M
      Add some sanity checks around usage of t_fromb64() · 73f0df83
      Matt Caswell 提交于
      The internal SRP function t_fromb64() converts from base64 to binary. It
      does not validate that the size of the destination is sufficiently large -
      that is up to the callers. In some places there was such a check, but not
      in others.
      
      Add an argument to t_fromb64() to provide the size of the destination
      buffer and validate that we don't write too much data. Also add some sanity
      checks to the callers where appropriate.
      
      With thanks to Shi Lei for reporting this issue.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      73f0df83
  6. 15 7月, 2016 1 次提交
  7. 18 6月, 2016 1 次提交
    • M
      constify SRP · 98370c2d
      Matt Caswell 提交于
      Add const qualifiers to lots of SRP stuff. This started out as an effort
      to silence some "type-punning" warnings on OpenBSD...but the fix was to
      have proper const correctness in SRP.
      
      RT4378
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      98370c2d
  8. 18 5月, 2016 1 次提交
  9. 29 4月, 2016 1 次提交
  10. 05 4月, 2016 2 次提交
  11. 10 3月, 2016 1 次提交
  12. 25 2月, 2016 1 次提交
    • E
      CVE-2016-0798: avoid memory leak in SRP · 380f18ed
      Emilia Kasper 提交于
      The SRP user database lookup method SRP_VBASE_get_by_user had confusing
      memory management semantics; the returned pointer was sometimes newly
      allocated, and sometimes owned by the callee. The calling code has no
      way of distinguishing these two cases.
      
      Specifically, SRP servers that configure a secret seed to hide valid
      login information are vulnerable to a memory leak: an attacker
      connecting with an invalid username can cause a memory leak of around
      300 bytes per connection.
      
      Servers that do not configure SRP, or configure SRP but do not configure
      a seed are not vulnerable.
      
      In Apache, the seed directive is known as SSLSRPUnknownUserSeed.
      
      To mitigate the memory leak, the seed handling in SRP_VBASE_get_by_user
      is now disabled even if the user has configured a seed.
      
      Applications are advised to migrate to SRP_VBASE_get1_by_user. However,
      note that OpenSSL makes no strong guarantees about the
      indistinguishability of valid and invalid logins. In particular,
      computations are currently not carried out in constant time.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      380f18ed
  13. 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
  14. 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
  15. 08 12月, 2015 2 次提交
  16. 26 11月, 2015 1 次提交
  17. 21 9月, 2015 1 次提交
  18. 14 5月, 2015 1 次提交
  19. 11 5月, 2015 1 次提交
  20. 05 5月, 2015 1 次提交
    • R
      Use safer sizeof variant in malloc · b4faea50
      Rich Salz 提交于
      For a local variable:
              TYPE *p;
      Allocations like this are "risky":
              p = OPENSSL_malloc(sizeof(TYPE));
      if the type of p changes, and the malloc call isn't updated, you
      could get memory corruption.  Instead do this:
              p = OPENSSL_malloc(sizeof(*p));
      Also fixed a few memset() calls that I noticed while doing this.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      b4faea50
  21. 01 5月, 2015 1 次提交
    • R
      free cleanup 12 · 895cba19
      Rich Salz 提交于
      Don't check for NULL before calling free function.  This gets:
              NAME_CONSTRAINTS_free GENERAL_SUBTREE_free ECDSA_METHOD_free
              JPAKE_CTX_free OCSP_REQ_CTX_free SCT_free SRP_VBASE_free
              SRP_gN_free SRP_user_pwd_free TXT_DB_free
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      895cba19
  22. 29 4月, 2015 1 次提交
  23. 25 3月, 2015 2 次提交
  24. 04 2月, 2015 1 次提交
  25. 22 1月, 2015 1 次提交
  26. 30 6月, 2014 1 次提交
  27. 06 5月, 2014 1 次提交
  28. 04 6月, 2012 1 次提交
  29. 13 3月, 2011 2 次提交