Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (nike.apache.org: 74.125.82.47 is neither permitted nor
 denied by domain of lindeman@uw.edu)
MIME-Version: 1.0
Date: Thu, 6 Jan 2011 16:42:44 -0800
Message-ID: <AANLkTi=n9M7bn1j-=Oh18iSBFVSU9h=pWUDbh2Vz=dRh@mail.gmail.com>
Subject: Force Subversion to grab information from Mac OS X keychain
From: Kevin Lindeman <lindeman@uw.edu>
To: users@subversion.apache.org
Content-Type: multipart/alternative; boundary=0016e649c77078c13d049936e599

--0016e649c77078c13d049936e599
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am running Subversion on Mac OS X. I noticed that once I login correctly
for an https subversion URL, it will create a file in ~/.subversion/auth/
that seems to point Subversion to where it stores the authentication - in
this case, it has the realmstring, username, "passtype", which is set to
keychain. That makes it know that it should be using the keychain from then
on to remember the password.

I am trying to automate some subversion processes, so I launch subversion,
give it arguments arguments, and even set some environment variables (such
as SVN_SSH, which allows me to tell SVN how to launch ssh, ie: with a
special username).

Unfortunately, my automation has no way to intercept the password prompt for
an http url. I can intercept the SSH login prompt for svn+ssh by setting the
SSH_ASKPASS environment variable. I already have been automating the process
of adding the password to the keychain (using the realmstring format, so svn
can find it once it knows to find it in the keychain).

But it looks like I am missing that critical file in ~/.subversion/auth/
that has the "passtype" set to keychain. Is there a way I can force SVN to
always use that as the passtype, either with an argument or an environment
variable?

If not, is it possible to force the creation of that file with some magic
SVN command? I thought of just running an svn info with my login info as
arguments since I noticed that file is created on a successful login, but
unfortunately many servers don't request authorization for info requests so
that doesn't work.

I don't think I will be able to solve this by using a setting in the
subversion config file.

Thanks,
- Kevin

--0016e649c77078c13d049936e599
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi,</div><div><br></div><div>I am running Subversion on Mac OS X. I no=
ticed that once I login correctly for an https subversion URL, it will crea=
te a file in ~/.subversion/auth/ that seems to point Subversion to where it=
 stores the authentication - in this case, it has the realmstring, username=
, &quot;passtype&quot;, which is set to keychain. That makes it know that i=
t should be using the keychain from then on to remember the password.</div>
<div><br></div><div>I am trying to automate some subversion processes, so I=
 launch subversion, give it arguments arguments, and even set some environm=
ent variables (such as SVN_SSH, which allows me to tell SVN how to launch s=
sh, ie: with a special username).</div>
<div><br></div><div>Unfortunately, my automation has no way to intercept th=
e password prompt for an http url. I can intercept the SSH login prompt for=
 svn+ssh by setting the SSH_ASKPASS environment variable. I already have be=
en automating the process of adding the password to the keychain (using the=
 realmstring format, so svn can find it once it knows to find it in the key=
chain).</div>
<div><br></div><div>But it looks like I am missing that critical file in ~/=
.subversion/auth/ that has the &quot;passtype&quot; set to keychain. Is the=
re a way I can force SVN to always use that as the passtype, either with an=
 argument or an environment variable?</div>
<div><br></div><div>If not, is it possible to force the creation of that fi=
le with some magic SVN command? I thought of just running an svn info with =
my login info as arguments since I noticed that file is created on a succes=
sful login, but unfortunately many servers don&#39;t request authorization =
for info requests so that doesn&#39;t work.</div>
<div><br></div><div>I don&#39;t think I will be able to solve this by using=
 a setting in the subversion config file.</div><div><br></div><div>Thanks,<=
/div><div>- Kevin</div>

--0016e649c77078c13d049936e599--