Age | Commit message (Collapse) | Author | |
---|---|---|---|
2015-11-15 | tests: Disabled 889 and 890 until we support POP3 continuation responses | Steve Holme | |
As POP3 final and continuation responses both begin with a + character, and both the finalcode and contcode variables in SASLprotoc are set as such, we cannot tell the difference between them when we are expecting an optional continuation from the server such as the following: + something else from the server +OK final response Disabled these tests until such a time we can tell the responses apart. | |||
2015-11-15 | tests: Corrected typos from commit ba4d8f7eba | Steve Holme | |
2015-11-15 | tests: Added OAUTHBEARER failure response tests | Steve Holme | |
2015-11-15 | oauth2: Support OAUTHBEARER failures sent as continuation responses | Steve Holme | |
According to RFC7628 a failure message may be sent by the server in a base64 encoded JSON string as a continuation response. Currently only implemented for OAUTHBEARER and not XAUTH2. | |||
2015-11-15 | RELEASE-NOTES: synced with 808a17ee675 | Daniel Stenberg | |
2015-11-14 | tests: Renamed existing OAuth 2.0 (XOAUTH) tests | Steve Holme | |
2015-11-14 | tests: Added OAuth 2.0 (OAUTHBEARER) tests | Steve Holme | |
2015-11-14 | oauth2: Added support for OAUTHBEARER SASL mechanism to IMAP, POP3 and SNMP | Steve Holme | |
OAUTHBEARER is now the official "registered" SASL mechanism name for OAuth 2.0. However, we don't want to drop support for XOAUTH2 as some servers won't support the new mechanism yet. | |||
2015-11-13 | RELEASE-NOTES: recounted curl_easy_setopt() options | Daniel Stenberg | |
2015-11-13 | typecheck-gcc.h: add missing slist-using options | Daniel Stenberg | |
CURLOPT_RESOLVE and CURLOPT_PROXYHEADER were missing Also sorted the list. | |||
2015-11-13 | typecheck-gcc.h: added CURLOPT_CLOSESOCKETDATA | Daniel Stenberg | |
... and sorted curl_is_cb_data_option alphabetically | |||
2015-11-13 | openssl: Free modules on cleanup | Sebastian Pohlschmidt | |
Curl_ossl_init calls OPENSSL_load_builtin_modules() but Curl_ossl_cleanup doesn't make a call to free these modules. Bug: https://github.com/bagder/curl/issues/526 | |||
2015-11-13 | symbols-in-versions: Added new CURLOPTTYPE_STRINGPOINT alias | Steve Holme | |
...following commit aba281e762 to fix test 1119. | |||
2015-11-13 | curl: mark two more options strings for --libcurl output | Daniel Stenberg | |
2015-11-13 | typecheck-gcc.h: add some missing string types | Daniel Stenberg | |
Also sorted that list alphabetically | |||
2015-11-13 | curl.h: introducing the STRINGPOINT alias | Daniel Stenberg | |
As an alias for OBJECTPOINT. Provided to allow us to grep for all string options easier. | |||
2015-11-13 | cleanup: general removal of TODO (and similar) comments | Daniel Stenberg | |
They tend to never get updated anyway so they're frequently inaccurate and we never go back to revisit them anyway. We document issues to work on properly in KNOWN_BUGS and TODO instead. | |||
2015-11-13 | ftplistparser: remove empty function | Daniel Stenberg | |
2015-11-13 | openssl: remove #if check for 0.9.7 for ENGINE_load_private_key | Daniel Stenberg | |
2015-11-13 | openssl: all supported versions have X509_STORE_set_flags | Daniel Stenberg | |
Simplify by removing #ifdefs and macros | |||
2015-11-13 | openssl: remove 0.9.3 check | Daniel Stenberg | |
2015-11-13 | openssl: remove #ifdefs for < 0.9.5 support | Daniel Stenberg | |
We only support >= 0.9.7 | |||
2015-11-13 | lib/vtls/openssl: remove unused traces of yassl ifdefs | Daniel Stenberg | |
2015-11-12 | unit1603: Demote hash mismatch failure to a warning | dfandrich | |
The hashes can vary between architectures (e.g. Sparc differs from x86_64). This is not a fatal problem but just reduces the coverage of these white-box tests, as the assumptions about into which hash bucket each key falls are no longer valid. | |||
2015-11-12 | unit1603: Added unit tests for hash functions | dfandrich | |
2015-11-12 | unit1602: Fixed failure in torture test | dfandrich | |
2015-11-12 | sasl: Re-introduced XOAUTH2 in the default enabled authentication mechanism | Steve Holme | |
Following the fix in commit d6d58dd558 it is necessary to re-introduce XOAUTH2 in the default enabled authentication mechanism, which was removed in commit 7b2012f262, otherwise users will have to specify AUTH=XOAUTH2 in the URL. Note: OAuth 2.0 will only be used when the bearer is specified. | |||
2015-11-12 | sasl_sspi: fix identity memory leak in digest authentication | Stefan Bühler | |
2015-11-12 | sasl_sspi: fixed unicode build for digest authentication | Stefan Bühler | |
Closes #525 | |||
2015-11-12 | oauth2: Re-factored OAuth 2.0 state variable | Steve Holme | |
2015-11-12 | sasl: Don't choose OAuth 2.0 if mechanism not advertised | Steve Holme | |
Regression from commit 9e8ced9890 which meant if --oauth2-bearer was specified but the SASL mechanism wasn't supported by the server then the mechanism would be chosen. | |||
2015-11-12 | runtests: more compact "System characteristics" output | Daniel Stenberg | |
- no point in repeating curl features that is already listed as features from the curl -V output - remove the port numbers/unix domain path from the output unless verbose is used, as that is rarely interesting to users. | |||
2015-11-12 | runtests: rename conditional curl-features to $has_[name] | Daniel Stenberg | |
2015-11-11 | oauth2: Introduced support for host and port details | Steve Holme | |
Added support to the OAuth 2.0 message function for host and port, in order to accommodate the official OAUTHBEARER SASL mechanism which is to be added shortly. | |||
2015-11-11 | curl_setup.h: Removed duplicate CURL_DISABLE_RTSP when HTTP_ONLY defined | Steve Holme | |
2015-11-11 | cmake: Add missing feature macros in config header (Part 2) | Steve Holme | |
In addition to commit a215381c94 added the RTSP, RTMP and SMB protocols. | |||
2015-11-10 | cmake: Add missing feature macros in config header | Douglas Creager | |
The curl_config.h file can be generated either from curl_config.h.cmake or curl_config.h.in, depending on whether you're building using CMake or the autotools. The CMake template header doesn't include entries for all of the protocols that you can disable, which (I think) means that you can't actually disable those protocols when building via CMake. Closes #523 | |||
2015-11-10 | BoringSSL: Work with stricter BIO_get_mem_data() | Douglas Creager | |
BoringSSL implements `BIO_get_mem_data` as a function, instead of a macro, and expects the output pointer to be a `char **`. We have to add an explicit cast to grab the pointer as a `const char **`. Closes #524 | |||
2015-11-10 | http2: rectify the http2 version #if check | Daniel Stenberg | |
We need 1.0.0 or later. Also verified by configure. | |||
2015-11-09 | oauth2: Don't use XAUTH2 in OAuth 2.0 function name | Steve Holme | |
2015-11-09 | oauth2: Don't use XOAUTH2 in OAuth 2.0 variables | Steve Holme | |
2015-11-09 | oauth2: Use OAuth 2.0 rather than XOAUTH2 in comments | Steve Holme | |
When referring to OAuth 2.0 we should use the official name rather the SASL mechanism name. | |||
2015-11-09 | imap: avoid freeing constant string | Daniel Stenberg | |
The fix in 1a614c6c3 was wrong and would leed to free() of a fixed string. Pointed-out-by: Kamil Dudka | |||
2015-11-09 | ROADMAP: remove two items already done | Daniel Stenberg | |
2015-11-09 | RELEASE-NOTES: synced with 2200bf62054 | Daniel Stenberg | |
2015-11-09 | acinclude: Remove check for 16-bit curl_off_t | Jay Satiro | |
Because it's illogical to check for a 16-bit curl_off_t. Ref: https://github.com/bagder/curl/issues/425#issuecomment-154964205 | |||
2015-11-08 | tool: Fixed a memory leak on OOM introduced in 19cb0c4a | Dan Fandrich | |
2015-11-08 | imap: Don't check for continuation when executing a CUSTOMREQUEST | Justin Ehlert | |
Bug: https://github.com/bagder/curl/issues/486 Closes https://github.com/bagder/curl/pull/487 | |||
2015-11-07 | imap: checksrc: remove space after while before paren | Daniel Stenberg | |
2015-11-07 | checksrc.whitelist: "missing space after close paren" | Daniel Stenberg | |
... when it was within a string! |