Re: Subversion not running with Xcode 2.1 on remote server (svn://)
Re: Subversion not running with Xcode 2.1 on remote server (svn://)
- Subject: Re: Subversion not running with Xcode 2.1 on remote server (svn://)
- From: Scott Tooker <email@hidden>
- Date: Tue, 14 Jun 2005 13:19:53 -0700
Please file bug reports on these issues, our goal is to make your
development jobs easier, not get in your way :)
Scott
On Jun 14, 2005, at 12:18 PM, Brad BARCLAY wrote:
On Jun 14, 2005, at 14:15, Scott Tooker wrote:
Hi Scott:
Xcode 2.1 only supports key-based authentication, not password-
based authentication (we use ssh-agent to manage the public keys
when dealing with SSH).
And let me tell you why the current implementation of this is
problematic.
From what I can see, Xcode indiscriminately launches the ssh-
agent when it is loaded, causing a few problems:
0) Those of us who are already using ssh-agent wind up having
two copies of the agent running. Xcode only uses the one it
launches, which by default has no keys added to it, so it doesn't
work.
1) The session Xcode launches had no way of affecting the
SSH_AUTH_SOCK and SECURITYSESSIONID environment variables in new
Terminal instances, so running ssh-add won't work. In order to get
at the values for these environment variables from the Xcode
process tree, I had to write a CVS wrapper script which could dump
their contents so I could set them inside a terminal so I could add
my keys.
I've been running the freeware SSHKeychain for managing my keys
under ssh-agent, and Xcode 2.1's behaviour made authentication with
any of my CVS servers impossible. I had to write a wrapper script
for CVS to change the SSH_AUTH_SOCK environment variable to point
to my existing ssh-agent socket file, and then have Xcode call this
wrapper script in order to be able to authenticate against any SSH
servers while retaining use of SSHKeychain. I still have multiple
ssh-agents running, but at least the extra ones Xcode 2.1 initiates
aren't being used.
What it boils down to is this:
0) Xcode doesn't respect existing instances of ssh-agent which
may be running, and
1) There doesn't appear to be a straight forward way to add
keys to the instance of ssh-agent Xcode initiates.
IMO, the new implementation needs some work to resolve these
problematic areas. I haven't opened a bug report (yet -- one of my
projects is rolling out this week, so I've been a bit preoccupied
with other things), but can do so if you'd like.
Brad BARCLAY,
Lead Developer & Project Administrator,
The jSyncManager Project.
=-=-=-=-=-=-=-=-=-=
From the Mac OS X Desktop of Brad BARCLAY
E-Mail: email@hidden Web: http://
www.jsyncmanager.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden