Skip to content
  1. Sep 30, 2014
  2. Sep 26, 2014
  3. Sep 25, 2014
  4. Sep 23, 2014
  5. Sep 19, 2014
  6. Sep 18, 2014
  7. Sep 15, 2014
  8. Sep 13, 2014
  9. Sep 12, 2014
    • Daniel Stenberg's avatar
      libcurl-tutorial.3: fix GnuTLS link to thread-safety guidelines · 06b27ea2
      Daniel Stenberg authored
      The former link was turned into a 404 at some point.
      
      Reported-By: Askar Safin
      06b27ea2
    • Daniel Stenberg's avatar
      contributors.sh: split list of names at comma · 1b314a85
      Daniel Stenberg authored
      ... to support a list of names provided in a commit message.
      1b314a85
    • Ulrich Telle's avatar
      ntlm: Fixed HTTP proxy authentication when using Windows SSPI · 8ee18228
      Ulrich Telle authored
      Removed ISC_REQ_* flags from calls to InitializeSecurityContext to fix
      bug in NTLM handshake for HTTP proxy authentication.
      
      NTLM handshake for HTTP proxy authentication failed with error
      SEC_E_INVALID_TOKEN from InitializeSecurityContext for certain proxy
      servers on generating the NTLM Type-3 message.
      
      The flag ISC_REQ_CONFIDENTIALITY seems to cause the problem according
      to the observations and suggestions made in a bug report for the
      QT project (https://bugreports.qt-project.org/browse/QTBUG-17322).
      
      Removing all the flags solved the problem.
      
      Bug: http://curl.haxx.se/mail/lib-2014-08/0273.html
      Reported-by: Ulrich Telle
      Assisted-by: Steve Holme, Daniel Stenberg
      8ee18228
    • Ray Satiro's avatar
      newlines: fix mixed newlines to LF-only · 006b61eb
      Ray Satiro authored
      I use the curl repo mainly on Windows with the typical Windows git
      checkout which converts the LF line endings in the curl repo to CRLF
      automatically on checkout. The automatic conversion is not done on files
      in the repo with mixed line endings. I recently noticed some weird
      output with projects/build-openssl.bat that I traced back to mixed line
      endings, so I scanned the repo and there are files (excluding the
      test data) that have mixed line endings.
      
      I used this command below to do the scan. Unfortunately it's not as easy
      as git grep, at least not on Windows. This gets the names of all the
      files in the repo's HEAD, gets each of those files raw from HEAD, checks
      for mixed line endings of both LF and CRLF, and prints the name if
      mixed. I excluded path tests/data/test* because those can have mixed
      line endings if I understand correctly.
      
      for f in `git ls-tree --name-only --full-tree -r HEAD`;
      do if [ -n "${f##tests/data/test*}" ];
          then git show "HEAD:$f" | \
           ...
      006b61eb
  10. Sep 11, 2014
  11. Sep 10, 2014