[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Hmm, bug in the new auth system?

From: Branko Čibej <brane_at_xbc.nu>
Date: 2003-04-18 20:18:39 CEST

Ben Collins-Sussman wrote:

>Branko Čibej <brane@xbc.nu> writes:
>
>
>
>>Before the auth data moved from .svn/auth to ~/.subversion/auth, I could
>>do the following:
>>
>> svn co http://... --password=foo
>>
>>and all the .svn/auth directories got populated with the password.
>>
>>When I do that now, the auth data doesn't get stored in the new
>>location. Does that mean that the auth provider only stores the data if
>>it was used?
>>
>>
>
>Yeah, that's how it was always supposed to work. If the client never
>receives an auth challenge, then it never tries to fetch *or* store
>creds. When you pass --username or --password on the commandline,
>it's simply readying default credentials in case a challenge happens.
>
Ah, O.K.

>I'd argue that the old behavior was a bug. If you want to erase
>cached credentials, just delete them out of ~/.subversion/auth/.
>
>
No no, what I wanted to do was store the creedentials in advance;
similar to what "cvs login" does. But it's quite O.K. if they get stored
at first commit.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 18 20:19:30 2003

This is an archived mail posted to the Subversion Dev mailing list.