Subversion Users,
I am having trouble getting Subversion to work with the Gnome keyring
and would like some advice on how to troubleshoot the situation. At this
point I have tried everything I can find (Google, these archives), so I
need to find how/where things are failing.
I am using the svn+ssh protocol to access a server within my
organization. Even with what I understand is the proper configuration, I
am still prompted for my SSH password and Subversion never mentions a
keyring or asks for a keyring password. The environment is RHEL 6, so I
expected this to work out-of-the-box with the default svn. More
information is below.
Thank you very much for any suggestions on how to troubleshoot this.
Sincerely,
Aubrey Barnard
(not subscribed)
Subversion
--
I have compiled my own version of 1.6.19 (r1383947) with support for
Gnome keyring. (I would prefer to stick with 1.6 instead of 1.7 because
my organization uses 1.6 and I would rather remain as
compatible/flexible as possible--not paint myself into a version
corner.) I believe the compile was successful and includes the correct
support as strace shows libkeyutils.so.1,
libsvn_auth_gnome_keyring-1.so.0, libgnome-keyring.so.0 have been found.
$ grep -v '^#' ~/.subversion/config
[auth]
password-stores = gnome-keyring
store-passwords = yes
[helpers]
editor-cmd = emacs
[tunnels]
[miscellany]
[auto-props]
$ grep -v '^#' ~/.subversion/servers
[groups]
[global]
store-passwords = yes
store-plaintext-passwords = no
gnome-keyring-daemon
The Gnome keyring daemon is running and appears to have correctly
exported the necessary information. (I believe DBus isn't necessary.)
GNOME_KEYRING_PID=5037
GNOME_KEYRING_SOCKET=/tmp/keyring-s1MYHa/socket
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-uFRC7uTUOL,guid=d1c109c092852c804a5be05f00290c3b
Keyrings
I believe I have an appropriate keyring setup.
$ ~/opt/bin/keyring_tool --getdef
svn
$ ~/opt/bin/keyring_tool --info svn
Keyring locked : no
Auto lock on idle : no
Auto lock idle timeout : 0 (in sec)
