From: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
To: git@vger.kernel.org
Cc: peff@peff.net, sam@vilain.net
Subject: [PATCH v3 3/4] http: handle proxy proactive authentication
Date: Mon, 05 Mar 2012 16:19:40 +0100 [thread overview]
Message-ID: <4F54D98C.2070909@seap.minhap.es> (raw)
If http_proactive_auth flag is set and there is a username
but no password in the proxy url, then interactively ask for
the password.
This makes possible to not have the password written down in
http_proxy env var or in http.proxy config option.
Signed-off-by: Nelson Benitez Leon <nbenitezl@gmail.com>
---
http.c | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/http.c b/http.c
index 8932da5..b0b4362 100644
--- a/http.c
+++ b/http.c
@@ -43,6 +43,7 @@ static int curl_ftp_no_epsv;
static const char *curl_http_proxy;
static const char *curl_cookie_file;
static struct credential http_auth = CREDENTIAL_INIT;
+static struct credential proxy_auth = CREDENTIAL_INIT;
static int http_proactive_auth;
static const char *user_agent;
@@ -303,6 +304,17 @@ static CURL *get_curl_handle(void)
}
}
if (curl_http_proxy) {
+ credential_from_url(&proxy_auth, curl_http_proxy);
+ if (http_proactive_auth && proxy_auth.username && !proxy_auth.password) {
+ /* proxy string has username but no password, ask for password */
+ struct strbuf pbuf = STRBUF_INIT;
+ credential_fill(&proxy_auth);
+ strbuf_addf(&pbuf, "%s://%s:%s@%s",proxy_auth.protocol,
+ proxy_auth.username, proxy_auth.password,
+ proxy_auth.host);
+ free ((void *)curl_http_proxy);
+ curl_http_proxy = strbuf_detach(&pbuf, NULL);
+ }
curl_easy_setopt(result, CURLOPT_PROXY, curl_http_proxy);
curl_easy_setopt(result, CURLOPT_PROXYAUTH, CURLAUTH_ANY);
}
--
1.7.7.6
next reply other threads:[~2012-03-05 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 15:19 Nelson Benitez Leon [this message]
2012-03-06 8:30 ` [PATCH v3 3/4] http: handle proxy proactive authentication Jeff King
2012-03-06 10:58 ` Nelson Benitez Leon
2012-03-06 10:09 ` Jeff King
2012-03-06 10:53 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F54D98C.2070909@seap.minhap.es \
--to=nelsonjesus.benitez@seap.minhap.es \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sam@vilain.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.