1. 16 Jan, 2020 1 commit
  2. 17 Jan, 2020 2 commits
  3. 15 Jan, 2020 1 commit
  4. 03 Jan, 2020 1 commit
  5. 15 Jan, 2020 1 commit
  6. 14 Jan, 2020 1 commit
  7. 13 Jan, 2020 1 commit
  8. 14 Jan, 2020 5 commits
  9. 21 Dec, 2019 1 commit
  10. 13 Jan, 2020 1 commit
  11. 11 Jan, 2020 1 commit
  12. 07 Jan, 2020 2 commits
  13. 06 Jan, 2020 2 commits
  14. 03 Jan, 2020 1 commit
  15. 02 Jan, 2020 4 commits
  16. 01 Jan, 2020 1 commit
  17. 20 Dec, 2019 2 commits
  18. 19 Dec, 2019 1 commit
  19. 12 Dec, 2019 1 commit
  20. 18 Dec, 2019 2 commits
  21. 25 Nov, 2019 1 commit
  22. 12 Dec, 2019 1 commit
  23. 10 Dec, 2019 1 commit
  24. 11 Dec, 2019 1 commit
  25. 29 Nov, 2019 1 commit
    • Martin Thomson's avatar
      Bug 1600144 - Treat ClientHello with message_seq of 1 as a second ClientHello, r=kjacobs · 330d7efa
      Martin Thomson authored
      Summary:
      The logic that deals with stateless HelloRetryRequest in DTLS
      allows this one-off increment to the message_seq field in case the server was
      operating statelessly.  However, when it does, it should insist on the
      ClientHello carrying a cookie; concretely, it should set the flag that says that
      a HelloRetryRequest was sent, even if it doesn't currently remember that it sent
      one. That is the only way that this condition could be met.
      
      Differential Revision: https://phabricator.services.mozilla.com/D55210
      
      --HG--
      extra : rebase_source : 07acedf98f6619e53706a9c3a738a81198178747
      extra : amend_source : fb1f0cd771db8464901a9103f1b6989f94f71a20
      330d7efa
  26. 11 Dec, 2019 2 commits
  27. 09 Dec, 2019 1 commit