aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorSteve Holme <steve_holme@hotmail.com>2013-09-20 21:56:34 +0100
committerSteve Holme <steve_holme@hotmail.com>2013-09-20 21:56:30 +0100
commit18db7438512de1d6f63c616af5755ea2859597b8 (patch)
tree72c5678f29d94dd175dc78c9a46b04e8a2f83da4 /src
parent0e188e2dc339c6667eb954682a2bf768c6419aa9 (diff)
pop3: Added basic SASL XOAUTH2 support
Added the ability to use an XOAUTH2 bearer token [RFC6750] with POP3 for authentication using RFC6749 "OAuth 2.0 Authorization Framework". The bearer token is expected to be valid for the user specified in conn->user. If CURLOPT_XOAUTH2_BEARER is defined and the connection has an advertised auth mechanism of "XOAUTH2", the user and access token are formatted as a base64 encoded string and sent to the server as "AUTH XOAUTH2 <bearer token>".
Diffstat (limited to 'src')
-rw-r--r--src/tool_help.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/tool_help.c b/src/tool_help.c
index bd3cbb8a9..81f3bcdd7 100644
--- a/src/tool_help.c
+++ b/src/tool_help.c
@@ -47,7 +47,7 @@ static const char *const helptext[] = {
" --anyauth Pick \"any\" authentication method (H)",
" -a, --append Append to target file when uploading (F/SFTP)",
" --basic Use HTTP Basic Authentication (H)",
- " --bearer BEARER XOAUTH2 Bearer Token (IMAP and SMTP)",
+ " --bearer BEARER XOAUTH2 Bearer Token (IMAP, POP3, SMTP)",
" --cacert FILE CA certificate to verify peer against (SSL)",
" --capath DIR CA directory to verify peer against (SSL)",
" -E, --cert CERT[:PASSWD] Client certificate file and password (SSL)",