Re: non-interactive user authentication

Branko Čibej <brane@xbc.nu> writes:
> I have a few of those, too -- some of them do updates from
> repositories that require authentication for reading, not just for
> writing. I get by by either explicitly passing --password, or setting
> things up so that the auth info is populated in the working copies. If
> they're not very complex scripts, then I guess it's to be expected
> that they requre pretty precise set-up.

Hmmm. It's likely you didn't miss it the first time I said it, but
I'll reiterate just in case: no matter how carefully someone sets up
their client-side script, if they don't control the repository,
there's always the chance that something on the server will change and
the client will suddenly start prompting.

Which is why part of that "precise setup" may needs to involve passing
the --non-interactive option. (?)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 7 23:12:47 2002