git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [git-svn] always prompted for passphrase with subversion 1.6

From
TPTim Potter <tpot@hp.com>
Date
Sep 10, 2009, 00:58 UTC
Message-ID
<4AA84F46.6010706@hp.com>
In-Reply-To
<20090905064649.GD22272@dcvr.yhbt.net>
Eric Wong wrote:
Show 19 quoted lines
> 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.
Previous: Eric WongNext: Edward Rudd
Message 3 of 4 in “[git-svn] always prompted for passphrase with subversion 1.6”
  1. Tim PotterAug 27, 2009
  2. Eric WongSep 5, 2009
  3. Tim PotterSep 10, 2009
  4. Edward RuddDec 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.