I'm running into an issue where I have to enter my pem certificate password every time I git-svn fetch or git-svn dcommit. Vanilla svn uses OS X KeyChain and remembers my password just fine. Is there a known solution for this? Other users have ran into same issue as described here: http://stackoverflow.com/questions/605519/does-git-svn-store-svn-passwords. However, that solution of removing .subversion folder did not work for me.
Thanks,
Igor
From: Jakub Narebski <hidden> Date: 2016-06-15 22:53:06
Igor [off-list ref] writes:
I'm running into an issue where I have to enter my pem certificate
password every time I git-svn fetch or git-svn dcommit. Vanilla svn
uses OS X KeyChain and remembers my password just fine. Is there a
known solution for this? Other users have ran into same issue as
described here:
http://stackoverflow.com/questions/605519/does-git-svn-store-svn-passwords
However, that solution of removing .subversion folder did not work
for me.
I don't know if it is svn that has to remember password, or git that
has to remember password. Git 1.7.9 learned "credentials API" that
allows integration with platform native keychain mechanisms, and I
think OS X Keychain is one of examples / supported platforms (but it
might not made it into core git)... though I am not sure if it affects
git-svn, or only HTTP(S) transport.
--
Jakub Narebski
From: Eric Wong <hidden> Date: 2016-06-15 22:53:06
Igor [off-list ref] wrote:
I'm running into an issue where I have to enter my pem certificate
password every time I git-svn fetch or git-svn dcommit. Vanilla svn
uses OS X KeyChain and remembers my password just fine. Is there a
known solution for this? Other users have ran into same issue as
described here:
http://stackoverflow.com/questions/605519/does-git-svn-store-svn-passwords.
However, that solution of removing .subversion folder did not work for
me.
Hi Igor, this issue seems related to the platform specific auth
providers patches. There have been bugs in the SVN bindings in
previous releases and uncertainty about how everything works.
I haven't been interested enough to follow along closely[1], but maybe
some other folks Cc:-ed can finally push this through.
http://mid.gmane.org/20120103204403.GI17548@login.drsnuggles.stderr.nl
Basically I'm waiting for a patch that we can be certain won't break the
majority of existing use cases (especially no triggering of segfaults
and other nastiness in released versions of SVN bindings).
[1] - I barely use git-svn anymore, and wouldn't touch GNOME or OSX
with a 10-foot pole...
I'm running into an issue where I have to enter my pem certificate
password every time I git-svn fetch or git-svn dcommit. Vanilla svn
uses OS X KeyChain and remembers my password just fine. Is there a
known solution for this?
I don't know if it is svn that has to remember password, or git that
has to remember password. Git 1.7.9 learned "credentials API" that
allows integration with platform native keychain mechanisms, and I
think OS X Keychain is one of examples / supported platforms (but it
might not made it into core git)... though I am not sure if it affects
git-svn, or only HTTP(S) transport.
Wow, I just signed up to the mainling list to post about this, but it turns
out the latest message is exactly what I wanted to ask.
Like Eric wrote, I'm pretty sure it is svn that is meant to store the
password here and the perl bindings or the git-svn part fails to deal with
the os x keychain right. With pure svn the keychain authentication works
just fine. If I set up plaintext password storage in the svn configs, then
git svn is also able to store passwords.
There is also this macports ticket [1] that has been around for a while. But
that can only be fixed by an upstream fix here.
I would love to help to get this working, but I'm not sure how I can.
Cheers,
Nikolaus
[1] https://trac.macports.org/ticket/28329
--
View this message in context: http://git.661346.n2.nabble.com/git-svn-won-t-remember-pem-password-tp7295962p7298035.html
Sent from the git mailing list archive at Nabble.com.
From: Jeff King <hidden> Date: 2016-06-15 22:53:06
On Sat, Feb 18, 2012 at 03:30:00AM -0800, Jakub Narebski wrote:
Igor [off-list ref] writes:
quoted
I'm running into an issue where I have to enter my pem certificate
password every time I git-svn fetch or git-svn dcommit. Vanilla svn
uses OS X KeyChain and remembers my password just fine. Is there a
known solution for this? Other users have ran into same issue as
described here:
http://stackoverflow.com/questions/605519/does-git-svn-store-svn-passwords
quoted
However, that solution of removing .subversion folder did not work
for me.
I don't know if it is svn that has to remember password, or git that
has to remember password. Git 1.7.9 learned "credentials API" that
allows integration with platform native keychain mechanisms, and I
think OS X Keychain is one of examples / supported platforms (but it
might not made it into core git)... though I am not sure if it affects
git-svn, or only HTTP(S) transport.
It does not affect git-svn currently.
I have some thoughts on providing access to the credentials API for
scripts like git-svn (right now, it is accessible only by C git
programs). However, there is an important question: should password
prompting in git-svn behave like git, or behave like svn?
So far, it has been the latter, and I think that is reasonable. The
resource that requires the credentials is an svn repo, not a git repo,
so you are more likely to want to share credentials for it with real
svn, and not other git commands.
As to the lack of keychain support, it looks like libsvn should be
handling this for us. We simply give it a callback function that gets
called if the user needs prompted, but I would think things like the
keychain handling would happen before it gets to our prompt (and if I
understand it, for _some_ credential storage formats, it does). So
either there is a bug in libsvn, or we are somehow invoking it
incorrectly.
-Peff
On Sat, Feb 18, 2012 at 03:30:00AM -0800, Jakub Narebski wrote:
quoted
Igor [off-list ref] writes:
quoted
I'm running into an issue where I have to enter my pem certificate
password every time I git-svn fetch or git-svn dcommit. Vanilla svn
uses OS X KeyChain and remembers my password just fine. Is there a
known solution for this? Other users have ran into same issue as
described here:
http://stackoverflow.com/questions/605519/does-git-svn-store-svn-passwords
quoted
However, that solution of removing .subversion folder did not work
for me.
I don't know if it is svn that has to remember password, or git that
has to remember password. Git 1.7.9 learned "credentials API" that
allows integration with platform native keychain mechanisms, and I
think OS X Keychain is one of examples / supported platforms (but it
might not made it into core git)... though I am not sure if it affects
git-svn, or only HTTP(S) transport.
It does not affect git-svn currently.
I have some thoughts on providing access to the credentials API for
scripts like git-svn (right now, it is accessible only by C git
programs). However, there is an important question: should password
prompting in git-svn behave like git, or behave like svn?
So far, it has been the latter, and I think that is reasonable. The
resource that requires the credentials is an svn repo, not a git repo,
so you are more likely to want to share credentials for it with real
svn, and not other git commands.
IMHO a normal user would expect git-svn to store credentials in the same way as normal svn. I think this is the way it should be.
Best regards,
Nikolaus
I'm running into an issue where I have to enter my pem certificate
password every time I git-svn fetch or git-svn dcommit. Vanilla svn
uses OS X KeyChain and remembers my password just fine. Is there a
known solution for this? Other users have ran into same issue as
described here:
http://stackoverflow.com/questions/605519/does-git-svn-store-svn-passwords.
However, that solution of removing .subversion folder did not work for
me.
I suspect this would be solved by including what svn calls "platform
specific authentication providers". This works on Linux, but I don't
have access to OSX for testing.
Could you test the patch I pasted below to see if this fixes your
problem? The patch is made against the git source tree (git master
version), but you should probably be able to apply it to your installed
git-svn file as well (it's just a perl script). I'm not sure where that
file lives on OSX though, it's /usr/lib/git-core/git-svn on my Linux
(Debian) system.
Eric, I think I got this feature sorted out finally (there is a second
patch for entering the gnome-keyring unlock password which required some
changes in the subversion bindings which got applied a while ago). Let's
see what the patch does for Igor and then I'll send over both patches
afterwards.
Gr.
Matthijs