From: Mark Lodato <lodatom@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 1/2] http.c: prompt for SSL client certificate password
Date: Thu, 4 Jun 2009 22:44:58 -0400 [thread overview]
Message-ID: <ca433830906041944s1a2b12en36eb88b23cb93a7c@mail.gmail.com> (raw)
In-Reply-To: <1243480563-5954-1-git-send-email-lodatom@gmail.com>
Any thoughts on this? I would love to see this in git 1.6.4, and I
don't think it affects people who do not use certificates.
~ Mark
On Wed, May 27, 2009 at 11:16 PM, Mark Lodato<lodatom@gmail.com> wrote:
> If an SSL client certificate is enabled (via http.sslcert or
> GIT_SSL_CERT), prompt for the certificate password rather than
> defaulting to OpenSSL's password prompt. This causes the prompt to only
> appear once each run. Previously, OpenSSL prompted the user *many*
> times, causing git to be unusable over HTTPS with client-side
> certificates.
>
> Note that the password is stored in memory in the clear while the
> program is running. This may be a security problem if git crashes and
> core dumps.
>
> The user is always prompted, even if the certificate is not encrypted.
> This should be fine; unencrypted certificates are rare and a security
> risk anyway.
>
> Signed-off-by: Mark Lodato <lodatom@gmail.com>
> ---
>
> See http://osdir.com/ml/git/2009-02/msg03402.html for a discussion of
> this topic and an example showing how horrible the current password
> prompts are.
>
> The next patch adds an option to disable this feature. I split it into
> two commits in case the configuration option is not wanted.
>
> I did not create any tests because the existing http.sslcert option has
> no tests to begin with.
>
> I would really like to use git over HTTPS with client certs, but the
> current situation is just unusable. So, I'm hoping this gets included
> in git.git at some point. I would be happy to hear any comments people
> have about this patch series. Thanks!
>
>
> http.c | 40 +++++++++++++++++++++++++++++++++++++++-
> 1 files changed, 39 insertions(+), 1 deletions(-)
>
> diff --git a/http.c b/http.c
> index 2e3d649..1fc3444 100644
> --- a/http.c
> +++ b/http.c
> @@ -26,6 +26,8 @@ static long curl_low_speed_time = -1;
> static int curl_ftp_no_epsv;
> static const char *curl_http_proxy;
> static char *user_name, *user_pass;
> +static char *ssl_cert_password;
> +static int ssl_cert_password_required;
>
> static struct curl_slist *pragma_header;
>
> @@ -167,6 +169,22 @@ static void init_curl_http_auth(CURL *result)
> }
> }
>
> +static int has_cert_password(void)
> +{
> + if (ssl_cert_password != NULL)
> + return 1;
> + if (ssl_cert == NULL || ssl_cert_password_required != 1)
> + return 0;
> + /* Only prompt the user once. */
> + ssl_cert_password_required = -1;
> + ssl_cert_password = getpass("Certificate Password: ");
> + if (ssl_cert_password != NULL) {
> + ssl_cert_password = xstrdup(ssl_cert_password);
> + return 1;
> + } else
> + return 0;
> +}
> +
> static CURL *get_curl_handle(void)
> {
> CURL *result = curl_easy_init();
> @@ -189,6 +207,16 @@ static CURL *get_curl_handle(void)
>
> if (ssl_cert != NULL)
> curl_easy_setopt(result, CURLOPT_SSLCERT, ssl_cert);
> + if (has_cert_password())
> + curl_easy_setopt(result,
> +#if LIBCURL_VERSION_NUM >= 0x071700
> + CURLOPT_KEYPASSWD,
> +#elif LIBCURL_VERSION_NUM >= 0x070903
> + CURLOPT_SSLKEYPASSWD,
> +#else
> + CURLOPT_SSLCERTPASSWD,
> +#endif
> + ssl_cert_password);
> #if LIBCURL_VERSION_NUM >= 0x070902
> if (ssl_key != NULL)
> curl_easy_setopt(result, CURLOPT_SSLKEY, ssl_key);
> @@ -329,8 +357,11 @@ void http_init(struct remote *remote)
> if (getenv("GIT_CURL_FTP_NO_EPSV"))
> curl_ftp_no_epsv = 1;
>
> - if (remote && remote->url && remote->url[0])
> + if (remote && remote->url && remote->url[0]) {
> http_auth_init(remote->url[0]);
> + if (!prefixcmp(remote->url[0], "https://"))
> + ssl_cert_password_required = 1;
> + }
>
> #ifndef NO_CURL_EASY_DUPHANDLE
> curl_default = get_curl_handle();
> @@ -370,6 +401,13 @@ void http_cleanup(void)
> free((void *)curl_http_proxy);
> curl_http_proxy = NULL;
> }
> +
> + if (ssl_cert_password != NULL) {
> + memset(ssl_cert_password, 0, strlen(ssl_cert_password));
> + free(ssl_cert_password);
> + ssl_cert_password = NULL;
> + }
> + ssl_cert_password_required = 0;
> }
>
> struct active_request_slot *get_active_slot(void)
> --
> 1.6.3.1
>
>
next prev parent reply other threads:[~2009-06-05 2:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 3:16 [PATCH 1/2] http.c: prompt for SSL client certificate password Mark Lodato
2009-05-28 3:16 ` [PATCH 2/2] http.c: add http.sslCertNoPass option Mark Lodato
2009-06-05 2:44 ` Mark Lodato [this message]
2009-06-05 8:20 ` [PATCH 1/2] http.c: prompt for SSL client certificate password Constantine Plotnikov
2009-06-07 14:10 ` Mark Lodato
2009-06-11 23:00 ` Mark Lodato
2009-06-11 23:42 ` Nanako Shiraishi
2009-06-11 23:59 ` Junio C Hamano
2009-06-12 7:56 ` Daniel Stenberg
2009-06-12 15:38 ` Constantine Plotnikov
2009-06-12 16:50 ` Jakub Narebski
2009-06-12 21:49 ` Rogan Dawes
2009-06-12 23:11 ` Mark Lodato
2009-06-12 23:26 ` Mark Lodato
2009-06-13 0:31 ` Junio C Hamano
2009-06-13 0:49 ` Mark Lodato
2009-06-13 11:22 ` Daniel Stenberg
2009-06-11 23:56 ` Junio C Hamano
2009-06-12 22:31 ` Mark Lodato
2009-06-12 6:34 ` Junio C Hamano
2009-06-12 7:59 ` Daniel Stenberg
2009-06-12 23:13 ` Mark Lodato
2009-06-13 0:14 ` Junio C Hamano
2009-06-13 0:33 ` Mark Lodato
2009-06-13 1:12 ` Junio C Hamano
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=ca433830906041944s1a2b12en36eb88b23cb93a7c@mail.gmail.com \
--to=lodatom@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).