summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* libcurl.rc: include curl/curlver.h "correctly"bagder/libcurl-rcDaniel Stenberg2021-09-231-1/+1
| | | | | Reported-by: Vitaly Varyvdin Fixes #7765
* RELEASE-NOTES: syncedDaniel Stenberg2021-09-232-29/+18
| | | | Bumped curlver to 7.80.0-dev
* misc: fix typos in docs and commentsa13460542021-09-236-6/+6
| | | | | | | No user facing output from curl/libcurl is changed by this, just comments. Closes #7747
* ci: update Lift config to match requirements of curl buildThomas M. DuBuisson2021-09-233-5/+5
| | | | | | Also renamed Muse -> Lift, the new tool name. Closes #7761
* cleanup: constify unmodified static structsRikard Falkeborn2021-09-2310-20/+20
| | | | | | | Constify a number of static structs that are never modified. Make them const to show this. Closes #7759
* RELEASE-NOTES: syncedcurl-7_79_1Daniel Stenberg2021-09-221-4/+0
| | | | curl 7.79.1 release
* THANKS: added names from the 7.79.1 releaseDaniel Stenberg2021-09-221-0/+5
|
* test897: verify delivery of IMAP post-body header contentDaniel Stenberg2021-09-213-2/+79
| | | | | | | | | | | | | The "content" is delivered as "body" by curl, but the envelope continues after the body and the rest of it should be delivered as header. The IMAP server can now get 'POSTFETCH' set to include more data to include after the body and test 897 is done to verify that such "extra" header data is in fact delivered by curl as header. Ref: #7284 but fails to reproduce the issue Closes #7748
* KNOWN_BUGS: connection migration doesn't workDaniel Stenberg2021-09-191-0/+5
| | | | Closes #7695
* RELEASE-NOTES: syncedDaniel Stenberg2021-09-191-5/+19
|
* http: fix the broken >3 digit response code detectionDaniel Stenberg2021-09-173-6/+51
| | | | | | | | | | | | | When the "reason phrase" in the HTTP status line starts with a digit, that was treated as the forth response code digit and curl would claim the response to be non-compliant. Added test 1466 to verify this case. Regression brought by 5dc594e44f73b17 Reported-by: Glenn de boer Fixes #7738 Closes #7739
* strerror: use sys_errlist instead of strerror on WindowsJay Satiro2021-09-171-2/+2
| | | | | | | | | | | | | | | - Change Curl_strerror to use sys_errlist[errnum] instead of strerror to retrieve the error message on Windows. Windows' strerror writes to a static buffer and is not thread-safe. Follow-up to 2f0bb86 which removed most instances of strerror in favor of calling Curl_strerror (which calls strerror_r for other platforms). Ref: https://github.com/curl/curl/pull/7685 Ref: https://github.com/curl/curl/commit/2f0bb86 Closes https://github.com/curl/curl/pull/7735
* dist: provide lib/.checksrc in the tarballDaniel Stenberg2021-09-161-2/+2
| | | | | | | | | So that debug builds work (checksrc really) Reported-by: Marcel Raad Reported-by: tawmoto on github Fixes #7733 Closes #7734
* TODO: Improve documentation about fork safetyDaniel Stenberg2021-09-161-0/+5
| | | | Closes #6968
* hsts: CURLSTS_FAIL from hsts read callback should fail transferDaniel Stenberg2021-09-166-6/+34
| | | | | | | | | | ... and have CURLE_ABORTED_BY_CALLBACK returned. Extended test 1915 to verify. Reported-by: Jonathan Cardoso Fixes #7726 Closes #7729
* test1184: disableDaniel Stenberg2021-09-161-0/+2
| | | | | | | | | The test should be fine and it works for me repeated when run manually, but clearly it causes CI failures and it needs more research. Reported-by: RiderALT on github Fixes #7725 Closes #7732
* Curl_http2_setup: don't change connection data on repeat invokesDaniel Stenberg2021-09-161-6/+6
| | | | | | | | | | Regression from 3cb8a748670ab88c (releasde in 7.79.0). That change moved transfer oriented inits to before the check but also erroneously moved a few connection oriented ones, which causes problems. Reported-by: Evangelos Foutras Fixes #7730 Closes #7731
* RELEASE-NOTES: syncedDaniel Stenberg2021-09-162-274/+15
| | | | and bump to 7.79.1
* tests/sshserver.pl: make it work with openssh-8.7p1Kamil Dudka2021-09-161-14/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | ... by not using options with no argument where an argument is required: === Start of file tests/log/ssh_server.log curl_sshd_config line 6: no argument after keyword "DenyGroups" curl_sshd_config line 7: no argument after keyword "AllowGroups" curl_sshd_config line 10: Deprecated option AuthorizedKeysFile2 curl_sshd_config line 29: Deprecated option KeyRegenerationInterval curl_sshd_config line 39: Deprecated option RhostsRSAAuthentication curl_sshd_config line 40: Deprecated option RSAAuthentication curl_sshd_config line 41: Deprecated option ServerKeyBits curl_sshd_config line 45: Deprecated option UseLogin curl_sshd_config line 56: no argument after keyword "AcceptEnv" curl_sshd_config: terminating, 3 bad configuration options === End of file tests/log/ssh_server.log === Start of file log/sftp_server.log curl_sftp_config line 33: Unsupported option "rhostsrsaauthentication" curl_sftp_config line 34: Unsupported option "rsaauthentication" curl_sftp_config line 52: no argument after keyword "sendenv" curl_sftp_config: terminating, 1 bad configuration options Connection closed. Connection closed === End of file log/sftp_server.log Closes #7724
* hsts: handle unlimited expiryDaniel Stenberg2021-09-154-28/+47
| | | | | | | | | | | | | | | | | | | When setting a blank expire string, meaning unlimited, curl would pass TIME_T_MAX to getime_r() when creating the output, while on 64 bit systems such a large value cannot be convetered to a tm struct making curl to exit the loop with an error instead. It can't be converted because the year it would represent doesn't fit in the 'int tm_year' field! Starting now, unlimited expiry is instead handled differently by using a human readable expiry date spelled out as "unlimited" instead of trying to use a distant actual date. Test 1660 and 1915 have been updated to help verify this change. Reported-by: Jonathan Cardoso Fixes #7720 Closes #7721
* curl_multi_fdset: make FD_SET() not operate on sockets out of rangeDaniel Stenberg2021-09-152-13/+21
| | | | | | | | | | The VALID_SOCK() macro was made to only check for FD_SETSIZE if curl was built to use select(), even though the curl_multi_fdset() function always and unconditionally uses FD_SET and needs the check. Reported-by: 0xee on github Fixes #7718 Closes #7719
* FAQ: add GOPHERS + curl works on data, not filesDaniel Stenberg2021-09-151-4/+4
|
* RELEASE-NOTES: syncedcurl-7_79_0Daniel Stenberg2021-09-141-7/+39
| | | | For the 7.79.0 release
* THANKS: add contributors from 7.79.0 release cycleDaniel Stenberg2021-09-141-0/+26
|
* FAQ: add two dev related questionsDaniel Stenberg2021-09-141-0/+41
| | | | | | | | 8.1 Why does curl use C89? 8.2 Will curl be rewritten? Spell-checked-by: Paul Johnson Closes #7715
* zuul.d/jobs: disable three tests for *-openssl-disable-proxyDaniel Stenberg2021-09-131-0/+1
| | | | | | | ... as they mysteriously seem to permfail without being related to proxy. Closes #7714
* ftp,imap,pop3,smtp: reject STARTTLS server response pipeliningPatrick Monnerat2021-09-139-1/+236
| | | | | | | | | | | | | If a server pipelines future responses within the STARTTLS response, the former are preserved in the pingpong cache across TLS negotiation and used as responses to the encrypted commands. This fix detects pipelined STARTTLS responses and rejects them with an error. CVE-2021-22947 Bug: https://curl.se/docs/CVE-2021-22947.html
* ftp,imap,pop3: do not ignore --ssl-reqdPatrick Monnerat2021-09-137-36/+195
| | | | | | | | | | | | In imap and pop3, check if TLS is required even when capabilities request has failed. In ftp, ignore preauthentication (230 status of server greeting) if TLS is required. Bug: https://curl.se/docs/CVE-2021-22946.html CVE-2021-22946
* mqtt: clear the leftovers pointer when sending succeedsz2_ on hackerone2021-09-131-0/+4
| | | | | | CVE-2021-22945 Bug: https://curl.se/docs/CVE-2021-22945.html
* zuul: bump the rustls job to use v0.7.2Daniel Stenberg2021-09-131-1/+2
| | | | | | ... and add -lm when using a rust library. Closes #7701
* RELEASE-PROCEDURE: add release dates from now to 8.0.0 in 2023Daniel Stenberg2021-09-131-4/+5
|
* SECURITY-PROCESS: tweak a little to match current practicesDaniel Stenberg2021-09-131-10/+11
| | | | Closes #7713
* http_proxy: fix the User-Agent inclusion in CONNECTDaniel Stenberg2021-09-133-19/+130
| | | | | | | | | | | | It should not refer to the uagent string that is allocated and created for the end server http request, as that pointer may be cleared on subsequent CONNECT requests. Added test case 1184 to verify. Reported-by: T200proX7 on github Fixes #7705 Closes #7707
* Curl_hsts_loadcb: don't attempt to load if hsts wasn't initedDaniel Stenberg2021-09-121-1/+3
| | | | | | Reported-by: Jonathan Cardoso Fixes #7710 Closes #7711
* ngtcp2: fix build with ngtcp2 and nghttp3Tatsuhiro Tsujikawa2021-09-122-4/+8
| | | | | | | | | ngtcp2_conn_client_new and nghttp3_conn_client_new are now macros. Check the wrapped functions instead. ngtcp2_stream_close callback now takes flags parameter. Closes #7709
* write-out.d: clarify size_download/uploadDaniel Stenberg2021-09-121-2/+4
| | | | | | They show the number of "body" bytes transfered. Fixes #7702 Closes #7706
* http2: Curl_http2_setup needs to init stream data in all invokesDaniel Stenberg2021-09-111-12/+17
| | | | | | | | | | | | Thus function was written to avoid doing multiple connection data initializations, which is fine, but since it also initiates stream related data it is crucial that it doesn't skip those even if called again for the same connection. Solved by moving the stream initializations before the "doing-it-again" check. Reported-by: Inho Oh Fixes #7630 Closes #7692
* url: fix compiler warning in no-verbose buildsDaniel Stenberg2021-09-101-0/+2
| | | | | | Follow-up from 2f0bb864c12 Closes #7700
* non-ascii: fix build errors from strerror fixDaniel Stenberg2021-09-101-12/+10
| | | | | | Follow-up to 2f0bb864c12 Closes #7697
* parse_args: redo the warnings for --remote-header-name combosDaniel Stenberg2021-09-103-13/+13
| | | | | | | | ... to avoid the memory leak risk pointed out by scan-build. Follow-up from 7a3e981781d6c18a Closes #7698
* ngtcp2: adapt to new size defintions upstreamDaniel Stenberg2021-09-101-16/+3
| | | | | Reviewed-by: Tatsuhiro Tsujikawa Closes #7699
* rustls: add strerror.h includeDaniel Stenberg2021-09-101-1/+1
| | | | Follow-up to 2f0bb864c12
* docs: the security list is reached at security at curl.se nowDaniel Stenberg2021-09-102-5/+9
| | | | | | | Also update the FAQ section a bit to encourage users to rather submit security issues on hackerone than sending email. Closes #7689
* runtests: add option -u to error on server unexpectedly aliveMarc Hoersken2021-09-095-30/+102
| | | | | | | | | | | | | | | Let's try to actually handle the server unexpectedly alive case by first making them visible on CI builds as failures. This is needed to detect issues with killing of the test servers completely including nested process chains with multiple PIDs per test server (including bash and perl). On Windows/cygwin platforms this is especially helpful with debugging PID mixups due to cygwin using its own PID space. Reviewed-by: Daniel Stenberg Closes #7180
* opts docs: unify phrasing in NAME headerDaniel Stenberg2021-09-09134-246/+246
| | | | | | | | | | | | | - avoid writing "set ..." or "enable/disable ..." or "specify ..." *All* options for curl_easy_setopt() are about setting or enabling things and most of the existing options didn't use that way of description. - start with lowercase letter, unless abbreviation. For consistency. - Some additional touch-ups Closes #7688
* strerror.h: remove the #include from files not using itDaniel Stenberg2021-09-0912-13/+1
|
* lib: don't use strerror()Daniel Stenberg2021-09-098-22/+71
| | | | | | | | | | We have and provide Curl_strerror() internally for a reason: strerror() is not necessarily thread-safe so we should always try to avoid it. Extended checksrc to warn for this, but feature the check disabled by default and only enable it in lib/ Closes #7685
* cirrus: Add FreeBSD 13.0 job and disable sanitizer buildDaniel Gustafsson2021-09-081-9/+11
| | | | | | | | | | | | | As alluded to the in the now removed comment, a 13.0 image became available and is now ready to be used. The sanitizer builds were running on the 12.1 image which since has been removed from the config, leaving the builds not running at all. When enabled it turns out that they don't actually work due to very long timeouts in executing the tests, so keep the disabled for now but a bit more controlled. Closes #7592
* copyrights: update copyright year rangesDaniel Stenberg2021-09-089-9/+9
|
* RELEASE-NOTES: syncedDaniel Stenberg2021-09-081-11/+28
|
View Lorry Controller Status