Skip to contentSkip to conversation

always prompted for passphrase with subversion 1.6

git-svn Tim Potter 3 participants 4 messages Jun 15, 2016

lore
Share & tools
lore

Tim Potter

author
#0 lore raw

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.

Regards,

Tim.

#1 lore raw
Quoted 6 lines · Tim Potter

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.

Quoted 6 lines

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.

[1] and probably still so, though I have recently managed to set *something* up with SSL client certs and maybe it's done right. SSL is just one of those things that never really "clicked" for me (ssh on the other hand...)

Signature · 1 line
Eric Wong
author
#2 lore raw
Quoted 11 lines · Eric Wong
Quoted 10 lines · Tim Potter

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.

Quoted 8 lines
Quoted 2 lines

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.

#3 lore raw
Quoted 6 lines · Tim Potter

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.

I've been tracking subversion bug # 3612
(http://subversion.tigris.org/issues/show_bug.cfg?id=3612 ) which is on this issue of perl binding not supporting platform specific providers.

A patch was added into subversion 1.6.15 that finally adds bindings for perl to access this functionality via a call to SVN::Core::auth_get_platform_specific_client_providers and adding it's contents to the array returned by _auth_providers..

The "test" modification I did to git-svn is as follows.

sub _auth_providers () {
(

    SVN::Core::auth_get_platform_specific_client_providers(undef,undef),
    [
      SVN::Client::get_simple_provider(),
      .... the rest of the static provider ...
    ]

)
}

I'm honestly not sure if it should be at the beginning or end, and this also needs some run-time checking to determine if the user has at least SVN 1.6.15 installed