Skip to content
  1. Feb 10, 2011
  2. Jan 18, 2011
  3. Jan 04, 2011
  4. Jan 03, 2011
  5. Dec 15, 2010
  6. Dec 09, 2010
  7. Nov 19, 2010
  8. Nov 14, 2010
  9. Nov 09, 2010
  10. Nov 08, 2010
  11. Nov 04, 2010
  12. Oct 17, 2010
  13. Oct 12, 2010
  14. Oct 08, 2010
  15. Sep 30, 2010
  16. Sep 28, 2010
  17. Sep 21, 2010
  18. Sep 20, 2010
  19. Sep 18, 2010
  20. Sep 12, 2010
  21. Aug 25, 2010
  22. Aug 15, 2010
  23. Aug 11, 2010
  24. Aug 10, 2010
  25. Aug 06, 2010
  26. Aug 02, 2010
  27. Jul 14, 2010
  28. Jul 13, 2010
  29. Jun 30, 2010
    • Kamil Dudka's avatar
      http_ntlm: add support for NSS · f3b77e56
      Kamil Dudka authored
      When configured with '--without-ssl --with-nss', NTLM authentication
      now uses NSS crypto library for MD5 and DES.  For MD4 we have a local
      implementation in that case.  More details are available at
      https://bugzilla.redhat.com/603783
      
      In order to get it working, curl_global_init() must be called with
      CURL_GLOBAL_SSL or CURL_GLOBAL_ALL.  That's necessary because NSS needs
      to be initialized globally and we do so only when the NSS library is
      actually required by protocol.  The mentioned call of curl_global_init()
      is responsible for creating of the initialization mutex.
      
      There was also slightly changed the NSS initialization scenario, in
      particular, loading of the NSS PEM module.  It used to be loaded always
      right after the NSS library was initialized.  Now the library is
      initialized as soon as any SSL or NTLM is required, while the PEM module
      is prevented from being loaded until the SSL is actually required.
      f3b77e56
  30. Jun 28, 2010
  31. Jun 16, 2010
  32. Jun 05, 2010
    • Constantine Sapuntzakis's avatar
      OpenSSL: fix spurious SSL connection aborts · a0dd9df9
      Constantine Sapuntzakis authored
      Was seeing spurious SSL connection aborts using libcurl and
      OpenSSL. I tracked it down to uncleared error state on the
      OpenSSL error stack - patch attached deals with that.
      
      Rough idea of problem:
      
      Code that uses libcurl calls some library that uses OpenSSL but
      don't clear the OpenSSL error stack after an error.
      
      ssluse.c calls SSL_read which eventually gets an EWOULDBLOCK from
      the OS. Returns -1 to indicate an error
      
      ssluse.c calls SSL_get_error. First thing, SSL_get_error calls
      ERR_get_error to check the OpenSSL error stack, finds an old
      error and returns SSL_ERROR_SSL instead of SSL_ERROR_WANT_READ or
      SSL_ERROR_WANT_WRITE.
      
      ssluse.c returns an error and aborts the connection
      
      Solution:
      
      Clear the openssl error stack before calling SSL_* operation if
      we're going to call SSL_get_error afterwards.
      
      Notes:
      
      This is much more likely to happen with multi because it's easier
      to intersperse other calls to the OpenSSL library in the same
      thread.
      a0dd9df9