Skip to content
  1. Jan 29, 2014
    • Dr. Stephen Henson's avatar
      Clarify docs. · 8e04001f
      Dr. Stephen Henson authored
      Remove reference to ERR_TXT_MALLOCED in the error library as that is
      only used internally. Indicate that returned error data must not be
      freed.
      (cherry picked from commit f2d678e6)
      8e04001f
  2. Jan 28, 2014
  3. Jan 23, 2014
  4. Jan 16, 2014
  5. Jan 11, 2014
  6. Jan 10, 2014
  7. Jan 09, 2014
  8. Jan 06, 2014
  9. Jan 04, 2014
    • Dr. Stephen Henson's avatar
      Restore SSL_OP_MSIE_SSLV2_RSA_PADDING · 1b0d4812
      Dr. Stephen Henson authored
      The flag SSL_OP_MSIE_SSLV2_RSA_PADDING hasn't done anything since OpenSSL
      0.9.7h but deleting it will break source compatibility with any software
      that references it. Restore it but #define to zero.
      (cherry picked from commit b17d6b8d)
      1b0d4812
  10. Jan 02, 2014
  11. Dec 20, 2013
  12. Dec 10, 2013
  13. Dec 09, 2013
  14. Nov 27, 2013
  15. Nov 11, 2013
  16. Nov 09, 2013
  17. Nov 08, 2013
  18. Nov 06, 2013
  19. Nov 05, 2013
  20. Oct 04, 2013
  21. Oct 03, 2013
  22. Oct 01, 2013
  23. Sep 30, 2013
  24. Sep 16, 2013
    • Bodo Moeller's avatar
      Sync CHANGES and NEWS files. · f11bedf8
      Bodo Moeller authored
      f11bedf8
    • Bodo Moeller's avatar
      Fix overly lenient comparisons: · c23746f3
      Bodo Moeller authored
          - EC_GROUP_cmp shouldn't consider curves equal just because
            the curve name is the same. (They really *should* be the same
            in this case, but there's an EC_GROUP_set_curve_name API,
            which could be misused.)
      
          - EC_POINT_cmp shouldn't return 0 for ERR_R_SHOULD_NOT_HAVE_BEEN_CALLED
            or EC_R_INCOMPATIBLE_OBJECTS errors because in a cmp API, 0 indicates
            equality (not an error).
      
          Reported by: king cope
      
      (cherry picked from commit 312a46791ab465cfa3bf26764361faed0e5df014)
      c23746f3
  25. Sep 10, 2013
  26. Sep 09, 2013
  27. Aug 20, 2013
  28. Aug 13, 2013
    • Michael Tuexen's avatar
      DTLS message_sequence number wrong in rehandshake ServerHello · 6f87807e
      Michael Tuexen authored
      This fix ensures that
      * A HelloRequest is retransmitted if not responded by a ClientHello
      * The HelloRequest "consumes" the sequence number 0. The subsequent
      ServerHello uses the sequence number 1.
      * The client also expects the sequence number of the ServerHello to
      be 1 if a HelloRequest was received earlier.
      This patch fixes the RFC violation.
      (cherry picked from commit b62f4daa)
      
      Conflicts:
      
      	ssl/d1_pkt.c
      6f87807e