1. 27 9月, 2017 2 次提交
  2. 26 6月, 2017 1 次提交
  3. 18 5月, 2016 1 次提交
  4. 08 3月, 2016 1 次提交
  5. 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
  6. 01 12月, 2015 1 次提交
  7. 10 11月, 2015 1 次提交
  8. 12 8月, 2015 1 次提交
  9. 01 8月, 2015 1 次提交
  10. 23 7月, 2015 1 次提交
  11. 14 5月, 2015 1 次提交
  12. 06 5月, 2015 1 次提交
  13. 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
  14. 29 4月, 2015 1 次提交
  15. 06 2月, 2015 1 次提交
  16. 22 1月, 2015 1 次提交
  17. 12 1月, 2015 1 次提交
  18. 08 12月, 2014 1 次提交
  19. 19 8月, 2014 1 次提交
  20. 07 5月, 2014 1 次提交
    • G
      bignum: allow concurrent BN_MONT_CTX_set_locked() · 12e9f627
      Geoff Thorpe 提交于
      The lazy-initialisation of BN_MONT_CTX was serialising all threads, as
      noted by Daniel Sands and co at Sandia. This was to handle the case that
      2 or more threads race to lazy-init the same context, but stunted all
      scalability in the case where 2 or more threads are doing unrelated
      things! We favour the latter case by punishing the former. The init work
      gets done by each thread that finds the context to be uninitialised, and
      we then lock the "set" logic after that work is done - the winning
      thread's work gets used, the losing threads throw away what they've done.
      Signed-off-by: NGeoff Thorpe <geoff@openssl.org>
      12e9f627
  21. 18 10月, 2011 2 次提交
  22. 19 3月, 2011 1 次提交
  23. 28 1月, 2011 1 次提交
  24. 27 1月, 2011 3 次提交
  25. 03 5月, 2008 1 次提交
  26. 02 5月, 2008 1 次提交
  27. 27 2月, 2008 1 次提交
  28. 19 9月, 2007 1 次提交
  29. 29 6月, 2007 1 次提交
  30. 11 6月, 2007 2 次提交
  31. 16 6月, 2006 1 次提交
  32. 14 6月, 2006 1 次提交
  33. 11 11月, 2005 1 次提交
  34. 23 10月, 2005 2 次提交