From: Rogan Dawes <lists@dawes.za.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Constantine Plotnikov <constantine.plotnikov@gmail.com>,
Daniel Stenberg <daniel@haxx.se>,
Nanako Shiraishi <nanako3@lavabit.com>,
Mark Lodato <lodatom@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] http.c: prompt for SSL client certificate password
Date: Fri, 12 Jun 2009 23:49:55 +0200 [thread overview]
Message-ID: <4A32CD83.1090801@dawes.za.net> (raw)
In-Reply-To: <m3vdn12y6y.fsf@localhost.localdomain>
Jakub Narebski wrote:
>> For SSH using unencrypted private key is very common for scripting and
>> cron jobs. For HTTPS situation looks like being worse since there is
>> no analog of ssh-agent that covers at least some of scripting
>> scenarios. Do we want to disable scripting for HTTPS?
>
> Actually you can use _encrypted_ private keys together with ssh-agent
> and for example keychain helper for scripting. You have to provide
> password to all listed private keys only once at login. I wonder if
> something like this would be possible for HTTP certificates...
I wonder if it might be possible using a PKCS#11 interface?
e.g. there are various "software" PKCS#11 implementations
(<http://trac.opendnssec.org/wiki/SoftHSM> springs to mind).
If you store your keys in the PKCS#11 store, and unlock them prior to
calling git, then the OpenSSL library might be able to access them
without a passphrase. Locking the PKCS#11 store would then secure the keys.
A little cumbersome, but possibly workable.
Rogan
next prev parent reply other threads:[~2009-06-12 21:51 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 ` [PATCH 1/2] http.c: prompt for SSL client certificate password Mark Lodato
2009-06-05 8:20 ` 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 [this message]
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=4A32CD83.1090801@dawes.za.net \
--to=lists@dawes.za.net \
--cc=constantine.plotnikov@gmail.com \
--cc=daniel@haxx.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=lodatom@gmail.com \
--cc=nanako3@lavabit.com \
/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).