On Tue, Jan 11, 2011 at 9:50 AM, Andy Levy <andy.levy_at_gmail.com> wrote:
> On Tue, Jan 11, 2011 at 12:42, NN Ott <nonot100_at_gmail.com> wrote:
> > Hi all,
> > If UserA checks out a working copy on to his machine, can UserB walk up
> to
> > that machine and the commit changes under his own credentials?
> > Would seem possible, but just wanted to double check if there are any pit
> > falls.
> > Thanks
>
> Credentials are cached in the user's home directory (~/.subversion,
> %APPDATA%\subversion), not in the working copy. If the 2 users have
> separate logins on the machine, then it's real easy. Otherwise, you
> can pass --username and --password command-line options.
>
> But I'd advise against encouraging this practice. In this scheme,
> UserA can make changes, and they'll be attributed to UserB in
> Subversion. A malicious UserA could cause a lot of trouble for UserB
> here.
>
FWIW I manually specify --username/--password all the time (needed for some
of our build scenarios) but I always specify --no-auth-cache to avoid
polluting the credentials cache for future users.
Kylo
Received on 2011-01-11 20:06:45 CET