sasl: Added calls to Curl_auth_is_<mechansism>_supported()

Hooked up the SASL authentication layer to query the new 'is mechanism
supported' functions when deciding what mechanism to use

sasl: Added calls to Curl_auth_is_<mechansism>_supported()

Hooked up the SASL authentication layer to query the new 'is mechanism
supported' functions when deciding what mechanism to use.

For now existing functionality is maintained.

show more ...

internals: rename the SessionHandle struct to Curl_easy

lib: include curl_printf.h as one of the last headers

curl_printf.h defines printf to curl_mprintf, etc. This can cause
problems with external headers which may use
__attribute__((fo

lib: include curl_printf.h as one of the last headers

curl_printf.h defines printf to curl_mprintf, etc. This can cause
problems with external headers which may use
__attribute__((format(printf, ...))) markers etc.

To avoid that they cause problems with system includes, we include
curl_printf.h after any system headers. That makes the three last
headers to always be, and we keep them in this order:

curl_printf.h
curl_memory.h
memdebug.h

None of them include system headers, they all do funny #defines.

Reported-by: David Benjamin

Fixes #743

show more ...

sasl: Fixed compilation errors from commit 9d89a0387

...when GSS-API or Windows SSPI are not used.

ftp/imap/pop3/smtp: Allow the service name to be overridden

Allow the service name to be overridden for DIGIST-MD5 and Kerberos 5
authentication in FTP, IMAP, POP3 and SMTP.

curl_sasl: Fixed potential null pointer utilisation

Although this should never happen due to the relationship between the
'mech' and 'resp' variables, and the way they are allocated toge

curl_sasl: Fixed potential null pointer utilisation

Although this should never happen due to the relationship between the
'mech' and 'resp' variables, and the way they are allocated together,
it does cause problems for code analysis tools:

V595 The 'mech' pointer was utilized before it was verified against
nullptr. Check lines: 376, 381. curl_sasl.c 376

Bug: https://github.com/curl/curl/issues/745
Reported-by: Alexis La Goutte

show more ...

krb5: Moved host from Curl_auth_create_gssapi_user_message() to be argument

For consistency with the spnego and oauth2 code moved the setting of
the host name outside of the Curl_auth_cr

krb5: Moved host from Curl_auth_create_gssapi_user_message() to be argument

For consistency with the spnego and oauth2 code moved the setting of
the host name outside of the Curl_auth_create_gssapi_user_messag()
function.

This will allow us to more easily override it in the future.

show more ...

vauth: Refactored function names after move to new vauth directory

Renamed all the SASL functions that moved to the new vauth directory to
include the correct module name.

vauth: Moved the OAuth 2.0 authentication code to the new vauth directory

vauth: Moved the NTLM authentication code to the new vauth directory

vauth: Moved the DIGEST authentication code to the new vauth directory

vauth: Moved the CRAM-MD5 authentication code to the new vauth directory

vauth: Moved the ClearText authentication code to the new vauth directory

vauth: Moved Curl_sasl_build_spn() to create the initial vauth source files

ftp/imap/pop3/smtp: Fixed compilation warning when /Wall enabled

warning C4706: assignment within conditional expression

curl_sasl.c: minor code indent fixes

digest: Use boolean based success code for Curl_sasl_digest_get_pair()

Rather than use a 0 and 1 integer base result code use a TRUE / FALSE
based success code.

digest: Corrected some typos in comments

ntlm: Corrected some typos in function descriptions

curl_sasl: Fix memory leak in digest parser

If any parameter in a HTTP DIGEST challenge message is present multiple
times, memory allocated for all but the last entry should be freed.

curl_sasl: Fix memory leak in digest parser

If any parameter in a HTTP DIGEST challenge message is present multiple
times, memory allocated for all but the last entry should be freed.

Bug: https://github.com/curl/curl/pull/667

show more ...

URLs: change all http:// URLs to https://

sasl; fix checksrc warnings

oauth2: Support OAUTHBEARER failures sent as continuation responses

According to RFC7628 a failure message may be sent by the server in a
base64 encoded JSON string as a continuation res

oauth2: Support OAUTHBEARER failures sent as continuation responses

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.

show more ...

oauth2: Added support for OAUTHBEARER SASL mechanism to IMAP, POP3 and SNMP

OAUTHBEARER is now the official "registered" SASL mechanism name for
OAuth 2.0. However, we don't want to drop

oauth2: Added support for OAUTHBEARER SASL mechanism to IMAP, POP3 and SNMP

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.

show more ...

sasl: Re-introduced XOAUTH2 in the default enabled authentication mechanism

Following the fix in commit d6d58dd558 it is necessary to re-introduce
XOAUTH2 in the default enabled authenti

sasl: Re-introduced XOAUTH2 in the default enabled authentication mechanism

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.

show more ...