1. 21 Aug, 2018 5 commits
  2. 31 Jul, 2018 1 commit
  3. 11 Jul, 2018 1 commit
  4. 10 Jul, 2018 1 commit
    • Nick Mathewson's avatar
      Rename torlog.[ch] to log.[ch] · e7f5f48d
      Nick Mathewson authored
      Fun fact: these files used to be called log.[ch] until we ran into
      conflicts with systems having a log.h file.  But now that we always
      include "lib/log/log.h", we should be fine.
      e7f5f48d
  5. 03 Jul, 2018 1 commit
  6. 28 Jun, 2018 1 commit
  7. 22 Jun, 2018 3 commits
  8. 21 Jun, 2018 2 commits
  9. 20 Jun, 2018 3 commits
  10. 08 May, 2018 1 commit
  11. 03 May, 2018 1 commit
  12. 27 Apr, 2018 1 commit
  13. 18 Apr, 2018 1 commit
  14. 06 Apr, 2018 1 commit
  15. 07 Feb, 2018 1 commit
  16. 03 Feb, 2018 1 commit
  17. 23 Jan, 2018 1 commit
    • Nick Mathewson's avatar
      Make Tor support TLS1.3 ciphers with OpenSSL 1.1.1 · 0dbe3ddc
      Nick Mathewson authored
      Without this patch, not only will TLS1.3 not work with Tor, but
      OpenSSL 1.1.1 with TLS1.3 enabled won't build any connections at
      all: It requires that either TLS1.3 be disabled, or some TLS1.3
      ciphersuites be listed.
      
      Closes ticket 24978.
      0dbe3ddc
  18. 13 Dec, 2017 1 commit
  19. 17 Nov, 2017 1 commit
  20. 28 Sep, 2017 1 commit
  21. 15 Sep, 2017 1 commit
  22. 09 Aug, 2017 1 commit
  23. 24 Jul, 2017 1 commit
  24. 05 Jun, 2017 3 commits
  25. 26 May, 2017 1 commit
  26. 31 Mar, 2017 2 commits
  27. 15 Mar, 2017 1 commit
  28. 27 Feb, 2017 1 commit
    • Nick Mathewson's avatar
      Revise the logic for picking the start time for link certs · f6e5a658
      Nick Mathewson authored
      Since 0.2.4.11-alpha (in 01966479) we've tried to randomize
      the start time to up to some time in the past.  But unfortunately we
      allowed the start time to be in the future as well, which isn't
      really legit.
      
      The new behavior lets the start time be be up to
      MAX(cert_lifetime-2days, 0) in the past, but never in the future.
      
      Fixes bug 21420; bugfix on 0.2.4.11-alpha.
      f6e5a658