Re: Xcode 3 losing scm password
Re: Xcode 3 losing scm password
- Subject: Re: Xcode 3 losing scm password
- From: kwiley <email@hidden>
- Date: Mon, 5 May 2008 10:15:42 -0700
On May 2, 2008, at 5:11 PM, j o a r wrote:
On May 2, 2008, at 12:54 PM, kwiley wrote:
There is no keychain named login. There are a set of categories on
the left however:
Hit the button in the lower left corner of the window to reveal the
actual keychains. If you don't have a keychain named "login", you
should still see one keychain with a name in bold, that's the
default keychain, and the one you should pay special attention to.
Yep, login is in bold, seems good to go. It has a subversion password
entry. If I open that record the subversion repository information is
correct and access control is set to allow Xcode to use it. How much
simpler could it be, right?
You could also try to run:
Keychain Access > Keychain First Aid
<sigh> I have already done this many times (no disrespect, it's good
advice, thank you). No problems found. Yet, if I enter a password
into Xcode's repository info, apply the changes, see the repository go
"green", quite Xcode, and launch again, the password field is empty
and SCM errors pop up until I fix it.
...ok, I give up...
I will stop asking questions about this on this list. Everyone has
been very helpful, but I have been trying to solve this problem for
several weeks now and no one knows how to solve it. Either Xcode or
Keychain is severely broken. I wish I could just skirt the whole
Keychain issue and have Xcode store the password that I enter into the
Xcode's own repository dialog. There is no excuse for the program
simply ignoring or forgetting the text that I enter into a field.
This is one of those problems that arises when developers try to make
their software too fancy and too intelligent...and then it breaks and
doesn't even exhibit basic functionality. Yes, it would be more
secure to store the password in the keychain, but if that isn't going
to work, then the fallback behavior is for the value in the textfield
to be preserved in some basic fashion, just write it to a preferences
file...but no, it has to interact with the keychain and Apple won't
have it any other way, so now it's fundamentally broken and I can't
use subversion with Xcode without manually opening the repository
settings and reentering the password every time I launch Xcode. The
program tries to be *too* smart, and ends up dumber than a basic
textfield saving program would be, whose behavior would be sufficient
for my purposes.
In the pursuit of ever cooler features (tying all passwords for all
applications across a single account together in some conglomerated
system-level protocol), developers should never regress a project
backward in performance to a level of functionality that precedes what
a simpler version could accomplish (remember the value entered into a
text field and regurgitate it at a later time). The latter approach
may be less secure, but guess what, the software exhibits the correct
behavior!
I guess I could always reinstall the system, or make a new user
account...maybe I can completely nuke then entire keychain somehow (I
already tried deleting the particular password in question from
keychain and regenerating it from scratch through Xcode, to no avail
of course).
Thank you for all your help, you have been patient and ingenuitive. I
appreciate all the suggestions.
Cheers!
________________________________________________________________________
Keith Wiley email@hidden http://www.cs.unm.edu/~kwiley
"I do not feel obliged to believe that the same God who has endowed us
with sense, reason, and intellect has intended us to forgo their use."
-- Galileo Galilei
________________________________________________________________________
_______________________________________________
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