From: Tim Potter <tpot@hp.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [git-svn] always prompted for passphrase with subversion 1.6
Date: Thu, 10 Sep 2009 10:58:46 +1000 [thread overview]
Message-ID: <4AA84F46.6010706@hp.com> (raw)
In-Reply-To: <20090905064649.GD22272@dcvr.yhbt.net>
Eric Wong wrote:
> Tim Potter <tpot@hp.com> wrote:
>> Hi everyone. I am using git-svn with the Subversion 1.6 client compiled
>> with GNOME Keyring support. This neat features allows a SSL client
>> certificate password to be cached inside GNOME Keyring instead of being
>> prompted to enter it every time. However the git-svn script doesn't
>> appear to know about this and always prompts for a password.
>>
>> Obviously there's some tweak required in the _auth_providers()
>> subroutine but I don't know enough about the Subversion Perl client to
>> figure out a fix.
>>
>> Has anyone else run in to this problem? I did a quick search on the
>> list but didn't find anything relevant.
>
> Hi Tim,
>
> I think one user wanted to get SSL certificate authentication going but
> my SSL knowledge was too weak at the time[1] and I think we both forgot
> about it or lost interest.
Hi Eric. Thanks for the reply.
It's probably just a matter of adding another entry to the
_auth_providers() function in git-svn. My thought was that there might
be a new auth provider in the Subversion 1.6 client library for GNOME
Keyring support that could be used for this.
I'll have a search through and see what I can find.
Regards,
Tim.
next prev parent reply other threads:[~2009-09-10 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 0:38 [git-svn] always prompted for passphrase with subversion 1.6 Tim Potter
2009-09-05 6:46 ` Eric Wong
2009-09-10 0:58 ` Tim Potter [this message]
2010-12-14 14:33 ` Edward Rudd
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=4AA84F46.6010706@hp.com \
--to=tpot@hp.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.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 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).