1. 18 Jan, 2011 2 commits
  2. 04 Jan, 2011 1 commit
  3. 03 Jan, 2011 1 commit
  4. 15 Dec, 2010 2 commits
  5. 09 Dec, 2010 1 commit
  6. 19 Nov, 2010 1 commit
  7. 14 Nov, 2010 1 commit
  8. 09 Nov, 2010 1 commit
  9. 08 Nov, 2010 1 commit
  10. 04 Nov, 2010 1 commit
  11. 17 Oct, 2010 1 commit
  12. 12 Oct, 2010 2 commits
  13. 08 Oct, 2010 1 commit
  14. 30 Sep, 2010 1 commit
  15. 28 Sep, 2010 1 commit
  16. 21 Sep, 2010 2 commits
  17. 20 Sep, 2010 1 commit
  18. 18 Sep, 2010 1 commit
  19. 12 Sep, 2010 1 commit
  20. 25 Aug, 2010 1 commit
  21. 15 Aug, 2010 2 commits
  22. 11 Aug, 2010 2 commits
  23. 10 Aug, 2010 1 commit
  24. 06 Aug, 2010 1 commit
  25. 02 Aug, 2010 1 commit
  26. 14 Jul, 2010 1 commit
  27. 13 Jul, 2010 1 commit
  28. 30 Jun, 2010 1 commit
    • 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
  29. 28 Jun, 2010 2 commits
  30. 16 Jun, 2010 1 commit
  31. 05 Jun, 2010 1 commit
    • 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
  32. 04 Jun, 2010 2 commits