From: Tzafrir Cohen <tzafrir.cohen@xorcom.com>
To: git@vger.kernel.org
Subject: git-svn and http client-side certificates
Date: Sat, 31 May 2008 10:42:42 +0300 [thread overview]
Message-ID: <20080531074240.GA13780@xorcom.com> (raw)
Hi
How do I make git-svn authenticate with client-side certificates?
Using strace, I can see that it reads my ~/.subversion/servers file and
checks my (encrypted) certificate. But then ssl_client_cert_pw is called
rather than ssl_client_cert (both are from Git::SVN::Prompt).
I couldn't find any useful hints.
I had a similar problem with Svk. I ended up patching SVN::Mirror::Ra to
behave differently in the presence of a specific environment variable,
which is quite non-elegant: the subversion client should know when to
use a certificate.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen@xorcom.com
+972-50-7952406 mailto:tzafrir.cohen@xorcom.com
http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir
reply other threads:[~2008-05-31 8:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080531074240.GA13780@xorcom.com \
--to=tzafrir.cohen@xorcom.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).