moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-10 11:35:07 -05:00
Code Issues Releases Wiki Activity
2838362a7b
curl/RELEASE-NOTES

61 lines
2.6 KiB
Plaintext
Raw Normal View History

start climbing to 7.19.6
2009-05-18 03:58:00 -04:00
Curl and libcurl 7.19.6
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
start climbing to 7.19.6
2009-05-18 03:58:00 -04:00
Public curl releases: 112
- Craig A West brought us: libcurl now defaults to do CONNECT with HTTP version 1.1 instead of 1.0 like before. This change also introduces the new proxy type for libcurl called 'CURLPROXY_HTTP_1_0' that then allows apps to switch (back) to CONNECT 1.0 requests. The curl tool also got a --proxy1.0 option that works exactly like --proxy but sets CURLPROXY_HTTP_1_0. I updated all test cases cases that use CONNECT and I tried to do some using --proxy1.0 and some updated to do CONNECT 1.1 to get both versions run.
2009-02-02 11:19:23 -05:00
Command line options: 132
- David Kierznowski notified us about a security flaw (http://curl.haxx.se/docs/adv_20090303.html also known as CVE-2009-0037) in which previous libcurl versions (by design) can be tricked to access an arbitrary local/different file instead of a remote one when CURLOPT_FOLLOWLOCATION is enabled. This flaw is now fixed in this release together this the addition of two new setopt options for controlling this new behavior: o CURLOPT_REDIR_PROTOCOLS controls what protocols libcurl is allowed to follow to when CURLOPT_FOLLOWLOCATION is enabled. By default, this option excludes the FILE and SCP protocols and thus you nee to explicitly allow them in your app if you really want that behavior. o CURLOPT_PROTOCOLS controls what protocol(s) libcurl is allowed to fetch using the primary URL option. This is useful if you want to allow a user or other outsiders control what URL to pass to libcurl and yet not allow all protocols libcurl may have been built to support.
2009-03-02 18:05:31 -05:00
curl_easy_setopt() options: 163
- Introducing curl_easy_send() and curl_easy_recv(). They can be used to send and receive data over a connection previously setup with curl_easy_perform() and its CURLOPT_CONNECT_ONLY option. The sendrecv.c example was added to show how they can be used.
2008-05-12 17:43:24 -04:00
Public functions in libcurl: 58
the Eiffel binding
2009-03-02 04:03:11 -05:00
Known libcurl bindings: 38
15 additional contributor from the 7.19.4 RELEASE-NOTES
2009-03-03 05:41:11 -05:00
Contributors: 715
David Hull made the file: URL parser also accept the somewhat sloppy file syntax: file:/path. I added test case 203 to verify this.
2003-10-29 04:53:21 -05:00
Armel Asselin made the CURLOPT_PREQUOTE option work fine even when CURLOPT_NOBODY is set true. PREQUOTE is then run roughly at the same place in the command sequence as it would have run if there would've been a transfer.
2006-08-08 18:56:46 -04:00
This release includes the following changes:
mention the curl_off_t changes first
2008-09-01 10:27:24 -04:00
- Markus Koetter made CURLOPT_FTPPORT (and curl's -P/--ftpport) support a port range if given colon-separated after the host name/address part. Like "192.168.0.1:2000-10000"
2009-06-29 16:46:01 -04:00
o CURLOPT_FTPPORT (and curl's -P/--ftpport) support port ranges
- Added CURLOPT_SSH_KNOWNHOSTS, CURLOPT_SSH_KEYFUNCTION, CURLOPT_SSH_KEYDATA. They introduce known_host support for SSH keys to libcurl. See docs for details.
2009-07-22 18:49:01 -04:00
o Added CURLOPT_SSH_KNOWNHOSTS, CURLOPT_SSH_KEYFUNCTION, CURLOPT_SSH_KEYDATA
- All the quote options (CURLOPT_QUOTE, CURLOPT_POSTQUOTE and CURLOPT_PREQUOTE) now accept a preceeding asterisk before the command to send when using FTP, as a sign that libcurl shall simply ignore the response from the server instead of treating it as an error. Not treating a 400+ FTP response code as an error means that failed commands will not abort the chain of commands, nor will they cause the connection to get disconnected.
2009-07-27 14:36:56 -04:00
o CURLOPT_QUOTE, CURLOPT_POSTQUOTE and CURLOPT_PREQUOTE can be told to ignore
error responses when used with FTP
Armel Asselin made the CURLOPT_PREQUOTE option work fine even when CURLOPT_NOBODY is set true. PREQUOTE is then run roughly at the same place in the command sequence as it would have run if there would've been a transfer.
2006-08-08 18:56:46 -04:00
HTTP Digest auth fix on a re-used connection
2007-07-22 06:17:52 -04:00
This release includes the following bugfixes:
- Kamil Dudka brought the patch from the Redhat bug entry https://bugzilla.redhat.com/show_bug.cgi?id=427966 which was libcurl closing a bad file descriptor when closing down the FTP data connection. Caolan McNamara seems to be the original author of it.
2009-05-19 16:54:31 -04:00
o crash on bad socket close with FTP
- bug report #2796358 (http://curl.haxx.se/bug/view.cgi?id=2796358) pointed out that the cookie parser would leak memory when it parses cookies that are received with domain, path etc set multiple times in the same header. While such a cookie is questionable, they occur in the wild and libcurl no longer leaks memory for them. I added such a header to test case 8.
2009-05-25 08:23:22 -04:00
o leaking cookie memory when duplicate domains or paths were used
- Frank McGeough provided a small OpenSSL #include fix to make libcurl compile fine with Nokia 5th edition 1.0 SDK for Symbian.
2009-05-27 17:11:11 -04:00
o build fix for Symbian
- Mike Crowe pointed out that setting CURLOPT_USERPWD to NULL used to clear the auth credentials back in 7.19.0 and earlier while now you have to set "" to get the same effect. His patch brings back the ability to use NULL.
2009-05-27 17:45:12 -04:00
o CURLOPT_USERPWD set to NULL clears auth credentials
- Claes Jakobsson fixed the configure script to better find and use NSS without pkg-config.
2009-06-01 05:40:09 -04:00
o libcurl-NSS build fixes
credit John E. Malmberg
2009-06-01 05:20:49 -04:00
o configure script fixed for VMS
- Setting the Content-Length: header from your app when you do a POST or PUT is almost always a VERY BAD IDEA. Yet there are still apps out there doing this, and now recently it triggered a bug/side-effect in libcurl as when libcurl sends a POST or PUT with NTLM, it sends an empty post first when it knows it will just get a 401/407 back. If the app then replaced the Content-Length header, it caused the server to wait for input that libcurl wouldn't send. Aaron Oneal reported this problem in bug report #2799008 http://curl.haxx.se/bug/view.cgi?id=2799008) and helped us verify the fix.
2009-06-05 02:18:42 -04:00
o set Content-Length: with POST and PUT failed with NTLM auth
allow building libcurl for VxWorks
2009-06-04 15:11:11 -04:00
o allow building libcurl for VxWorks
mention last changes
2009-06-05 12:32:37 -04:00
o curl tool exit codes fixed for VMS
- Eric Wong fixed --no-buffer to actually switch off output buffering. Been broken since 7.19.0
2009-06-07 18:21:22 -04:00
o --no-buffer treated correctly
djgpp build fix
2009-06-08 09:55:18 -04:00
o djgpp build fix
clarified configure detection of GnuTLS
2009-08-02 18:38:15 -04:00
o configure detection of GnuTLS now based on pkg-config as well
- Claes Jakobsson provided a patch for libcurl-NSS that fixed a bad refcount issue with client certs that caused issues like segfaults. http://curl.haxx.se/mail/lib-2009-05/0316.html
2009-06-08 17:25:16 -04:00
o libcurl-NSS client cert handling segfaults
- Eric Wong's patch: This allows curl(1) to be used as a client-side tunnel for arbitrary stream protocols by abusing chunked transfer encoding in both the HTTP request and HTTP response. This requires server support for sending a response while a request is still being read, of course. If attempting to read from stdin returns EAGAIN, then we pause our sender. This leaves curl to attempt to read from the socket while reading from stdin (and thus sending) is paused.
2009-06-15 17:13:00 -04:00
o curl uploading from stdin/pipes now works in non-blocking way so that it
continues the downloading even when the read stalls
- When doing non-anonymous ftp via http proxies and the password is not provided in the url, add it there (squid needs this).
2009-06-16 09:16:28 -04:00
o ftp credentials are added to the url if needed for http proxies
- Reuven Wachtfogel made curl -o - properly produce a binary output on windows (no newline translations). Use -B/--use-ascii if you rather get the ascii approach.
2009-06-16 14:03:28 -04:00
o curl -o - sends data to stdout using binary mode on windows
my CURLINFO_CERTINFO fix
2009-06-29 16:46:50 -04:00
o fixed the separators for "array" style string that CURLINFO_CERTINFO returns
- Constantine Sapuntzakis posted bug report #2813123 (http://curl.haxx.se/bug/view.cgi?id=2813123) and an a patch that fixes the problem: Url A is accessed using auth. Url A redirects to Url B (on a different server0. Url B reuses a persistent connection. Url B has auth, even though it's on a different server. Note: if Url B does not reuse a persistent connection, auth is not sent.
2009-07-08 03:00:40 -04:00
o auth problem over several hosts with re-used connection
- Added CURLOPT_SSH_KNOWNHOSTS, CURLOPT_SSH_KEYFUNCTION, CURLOPT_SSH_KEYDATA. They introduce known_host support for SSH keys to libcurl. See docs for details.
2009-07-22 18:49:01 -04:00
o improved the support for client certificates in libcurl+NSS
- David Binderman found a memory and fd leak in lib/gtls.c:load_file() (https://bugzilla.novell.com/523919). When looking at the code, I found that also the ptr pointer can leak.
2009-07-22 05:48:32 -04:00
o fix leak in gtls code
- Bug report #2825989 (http://curl.haxx.se/bug/view.cgi?id=2825989) pointed out that OpenSSL-powered libcurl didn't support the SHA-2 digest algorithm, and provided the solution too: to use OpenSSL_add_all_algorithms() instead of the older SSLeay_* alternative. OpenSSL_add_all_algorithms was added in OpenSSL 0.9.5
2009-07-26 13:33:36 -04:00
o missing algorithms in libcurl+OpenSSL
- Alexander Beedie provided the patch for a noproxy problem: If I have set CURLOPT_NOPROXY to "*", or to a host that should not use a proxy, I actually could still end up using a proxy if a proxy environment variable was set.
2009-08-01 07:02:10 -04:00
o with noproxy set you could still get a proxy if a proxy env was set
- Tanguy Fautre pointed out that OpenSSL's function RAND_screen() (present only in some OpenSSL installs - like on Windows) isn't thread-safe and we agreed that moving it to the global_init() function is a decent way to deal with this situation.
2009-08-01 07:09:02 -04:00
o rand seeding on libcurl on windows built with OpenSSL was not thread-safe
- Scott Cantor posted the bug report #2829955 (http://curl.haxx.se/bug/view.cgi?id=2829955) mentioning the recent SSL cert verification flaw found and exploited by Moxie Marlinspike. The presentation he did at Black Hat is available here: https://www.blackhat.com/html/bh-usa-09/bh-usa-09-archives.html#Marlinspike Apparently at least one CA allowed a subjectAltName or CN that contain a zero byte, and thus clients that assumed they would never have zero bytes were exploited to OK a certificate that didn't actually match the site. Like if the name in the cert was "example.com\0theatualsite.com", libcurl would happily verify that cert for example.com. libcurl now better use the length of the extracted name, not assuming it is zero terminated.
2009-08-01 17:56:59 -04:00
o fixed the zero byte inserted in cert name flaw in libcurl+OpenSSL
- Curt Bogmine reported a problem with SNI enabled on a particular server. We should introduce an option to disable SNI, but as we're in feature freeze now I've addressed the obvious bug here (pointed out by Peter Sylvester): we shouldn't try to enable SNI when SSLv2 or SSLv3 is explicitly selected. Code for OpenSSL and GnuTLS was fixed. NSS doesn't seem to have a particular option for SNI, or are we simply not using it?
2009-08-01 18:11:58 -04:00
o don't try SNI with SSLv2 or SSLv3 (OpenSSL and GnuTLS builds)
HTTP Digest auth fix on a re-used connection
2007-07-22 06:17:52 -04:00
This release includes the following known bugs:
o see docs/KNOWN_BUGS (http://curl.haxx.se/docs/knownbugs.html)
This release would not have looked like this without help, code, reports and
advice from friends like these:
- Setting the Content-Length: header from your app when you do a POST or PUT is almost always a VERY BAD IDEA. Yet there are still apps out there doing this, and now recently it triggered a bug/side-effect in libcurl as when libcurl sends a POST or PUT with NTLM, it sends an empty post first when it knows it will just get a 401/407 back. If the app then replaced the Content-Length header, it caused the server to wait for input that libcurl wouldn't send. Aaron Oneal reported this problem in bug report #2799008 http://curl.haxx.se/bug/view.cgi?id=2799008) and helped us verify the fix.
2009-06-05 02:18:42 -04:00
Yang Tse, Daniel Fandrich, Kamil Dudka, Caolan McNamara, Frank McGeough,
Andre Guibert de Bruet, Mike Crowe, Claes Jakobsson, John E. Malmberg,
initialize fread callback pointer to avoid compiler warning
2009-06-08 20:49:34 -04:00
Aaron Oneal, Igor Novoseltsev, Eric Wong, Bill Hoffman, Daniel Steinberg,
- Constantine Sapuntzakis posted bug report #2813123 (http://curl.haxx.se/bug/view.cgi?id=2813123) and an a patch that fixes the problem: Url A is accessed using auth. Url A redirects to Url B (on a different server0. Url B reuses a persistent connection. Url B has auth, even though it's on a different server. Note: if Url B does not reuse a persistent connection, auth is not sent.
2009-07-08 03:00:40 -04:00
Fabian Keil, Michal Marek, Reuven Wachtfogel, Markus Koetter,
- Tanguy Fautre pointed out that OpenSSL's function RAND_screen() (present only in some OpenSSL installs - like on Windows) isn't thread-safe and we agreed that moving it to the global_init() function is a decent way to deal with this situation.
2009-08-01 07:09:02 -04:00
Constantine Sapuntzakis, David Binderman, Johan van Selst, Alexander Beedie,
- Curt Bogmine reported a problem with SNI enabled on a particular server. We should introduce an option to disable SNI, but as we're in feature freeze now I've addressed the obvious bug here (pointed out by Peter Sylvester): we shouldn't try to enable SNI when SSLv2 or SSLv3 is explicitly selected. Code for OpenSSL and GnuTLS was fixed. NSS doesn't seem to have a particular option for SNI, or are we simply not using it?
2009-08-01 18:11:58 -04:00
Tanguy Fautre, Scott Cantor, Curt Bogmine, Peter Sylvester
start over on 7.18.1
2008-01-28 16:19:15 -05:00
working draft of the upcoming 7.10.8 release notes
2003-09-22 17:38:52 -04:00
Thanks! (and sorry if I forgot to mention someone)
Reference in New Issue Copy Permalink