Skip to content
  1. Mar 13, 2017
    • Matt Caswell's avatar
      Fix DTLSv1_listen() sequence numbers · 7321d794
      Matt Caswell authored
      
      
      DTLSv1_listen() is stateless. We never increment the record read sequence
      while listening, and we reflect the incoming record's sequence number in our
      write sequence.
      
      The logic for doing the write sequence reflection was *after* we had
      finished processing the incoming ClientHello and before we write the
      ServerHello. In the normal course of events this is fine. However if we
      need to write an early alert during ClientHello processing (e.g. no shared
      cipher), then we haven't done the write sequence reflection yet. This means
      the alert gets written with the wrong sequence number (it will just be set
      to whatever value we left it in the last time we wrote something). If the
      sequence number is less than expected then the client will believe that the
      incoming alert is a retransmit and will therefore drop it, causing the
      client to hang waiting for a response from the server.
      
      Fixes #2886
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/2915)
      7321d794
    • Richard Levitte's avatar
  2. Mar 12, 2017
  3. Mar 11, 2017
  4. Mar 10, 2017
  5. Mar 09, 2017
  6. Mar 08, 2017
  7. Mar 07, 2017
  8. Mar 03, 2017
  9. Feb 28, 2017
  10. Feb 27, 2017
  11. Feb 24, 2017
  12. Feb 23, 2017
  13. Feb 22, 2017
  14. Feb 21, 2017
  15. Feb 17, 2017
  16. Feb 16, 2017