From: "Jorge Lopez Silva via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Jorge <JALopezSilva@gmail.com>,
Jorge Lopez Silva <jalopezsilva@gmail.com>
Subject: [PATCH v2 2/2] config: documentation for HTTPS proxy client cert.
Date: Wed, 26 Feb 2020 23:23:58 +0000 [thread overview]
Message-ID: <c40207a3928f9cbc490b9ef2e99e7cba7788e7c0.1582759438.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.559.v2.git.1582759438.gitgitgadget@gmail.com>
From: Jorge Lopez Silva <jalopezsilva@gmail.com>
The commit adds 4 options, client cert, key, key password and CA info.
The CA info can be used to specify a different CA path to validate the
HTTPS proxy cert.
Signed-off-by: Jorge Lopez Silva <jalopezsilva@gmail.com>
---
Documentation/config/http.txt | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/Documentation/config/http.txt b/Documentation/config/http.txt
index e806033aab8..7e704687e87 100644
--- a/Documentation/config/http.txt
+++ b/Documentation/config/http.txt
@@ -29,6 +29,20 @@ http.proxyAuthMethod::
* `ntlm` - NTLM authentication (compare the --ntlm option of `curl(1)`)
--
+http.proxycert::
+ File indicating a client certificate to use to authenticate with an HTTPS proxy.
+
+http.proxykey::
+ File indicating a private key to use to authenticate with an HTTPS proxy.
+
+http.proxykeypass::
+ When communicating to the proxy using TLS (using an HTTPS proxy), use this
+ option along `http.proxykey` to indicate a password for the key.
+
+http.proxycainfo::
+ File containing the certificates to verify the proxy with when using an HTTPS
+ proxy.
+
http.emptyAuth::
Attempt authentication without seeking a username or password. This
can be used to attempt GSS-Negotiate authentication without specifying
--
gitgitgadget
next prev parent reply other threads:[~2020-02-26 23:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 21:36 [PATCH 0/2] Add HTTPS proxy SSL options (cert, key, cainfo) Jorge via GitGitGadget
2020-02-21 21:36 ` [PATCH 1/2] http: add client cert for HTTPS proxies Jorge Lopez Silva via GitGitGadget
2020-02-21 22:28 ` Eric Sunshine
2020-02-26 21:05 ` Jorge A López Silva
2020-02-21 21:36 ` [PATCH 2/2] config: documentation for HTTPS proxy client cert Jorge Lopez Silva via GitGitGadget
2020-02-26 23:23 ` [PATCH v2 0/2] Add HTTPS proxy SSL options (cert, key, cainfo) Jorge via GitGitGadget
2020-02-26 23:23 ` [PATCH v2 1/2] http: add client cert for HTTPS proxies Jorge Lopez Silva via GitGitGadget
2020-02-27 18:31 ` Junio C Hamano
2020-03-03 1:41 ` Jorge A López Silva
2020-02-26 23:23 ` Jorge Lopez Silva via GitGitGadget [this message]
2020-02-27 18:58 ` [PATCH v2 2/2] config: documentation for HTTPS proxy client cert Junio C Hamano
2020-03-03 1:47 ` Jorge A López Silva
2020-03-04 18:40 ` [PATCH v3 0/2] Add HTTPS proxy SSL options (cert, key, cainfo) Jorge via GitGitGadget
2020-03-04 18:40 ` [PATCH v3 1/2] http: add client cert for HTTPS proxies Jorge Lopez Silva via GitGitGadget
2020-03-04 18:40 ` [PATCH v3 2/2] http: add environment variable for HTTPS proxy Jorge Lopez Silva via GitGitGadget
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=c40207a3928f9cbc490b9ef2e99e7cba7788e7c0.1582759438.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=JALopezSilva@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).