Skip to content
  1. Feb 17, 2011
  2. Feb 13, 2011
  3. Feb 09, 2011
    • Quinn Slack's avatar
      CURLE_TLSAUTH_FAILED: removed · 3cffcba3
      Quinn Slack authored
      On second thought, I think CURLE_TLSAUTH_FAILED should be eliminated. It
      was only being raised when an internal error occurred while allocating
      or setting the GnuTLS SRP client credentials struct. For TLS
      authentication failures, the general CURLE_SSL_CONNECT_ERROR seems
      appropriate; its error string already includes "passwords" as a possible
      cause. Having a separate TLS auth error code might also cause people to
      think that a TLS auth failure means the wrong username or password was
      entered, when it could also be a sign of a man-in-the-middle attack.
      3cffcba3
    • Quinn Slack's avatar
      TLS-SRP: new options documented · ae7fe3b7
      Quinn Slack authored
      ae7fe3b7
  4. Feb 08, 2011
  5. Jan 31, 2011
  6. Jan 29, 2011
    • Daniel Stenberg's avatar
      FAQ: clarified/expanded 6.7 a bit · 819dfddc
      Daniel Stenberg authored
      "6.7 What are my obligations when using libcurl in my commercial apps?"
      got the piece about what exactly "in all copies" mean to a user of the
      code.
      
      This interpretation is based on what other MIT-like licenses have made
      more explicit.
      819dfddc
  7. Jan 27, 2011
  8. Jan 24, 2011
  9. Jan 21, 2011
  10. Jan 19, 2011
  11. Jan 18, 2011
  12. Jan 15, 2011
  13. Jan 12, 2011
  14. Jan 04, 2011
  15. Jan 03, 2011
  16. Dec 30, 2010
  17. Dec 25, 2010
  18. Dec 23, 2010
  19. Dec 22, 2010
  20. Dec 18, 2010
  21. Dec 17, 2010
  22. Dec 16, 2010
  23. Dec 15, 2010
  24. Dec 09, 2010
  25. Dec 08, 2010