From users-return-6933-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Tue Jan 11 19:06:34 2011 Return-Path: Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: (qmail 79147 invoked from network); 11 Jan 2011 19:06:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Jan 2011 19:06:34 -0000 Received: (qmail 23514 invoked by uid 500); 11 Jan 2011 19:06:34 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 23481 invoked by uid 500); 11 Jan 2011 19:06:33 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 23474 invoked by uid 99); 11 Jan 2011 19:06:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jan 2011 19:06:33 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kylo.ginsberg@gmail.com designates 209.85.216.43 as permitted sender) Received: from [209.85.216.43] (HELO mail-qw0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jan 2011 19:06:27 +0000 Received: by qwk3 with SMTP id 3so20311955qwk.16 for ; Tue, 11 Jan 2011 11:06:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=SYIYmioIeNKYoZ5u8eCdtm8yyxh/qbHgEmxT3fpMtlQ=; b=g3AScwnr2dPwPcQlQW0d1fgmnX5kyPZAX066AiyDdV+3TNAWX9tAIjg/DnBC2FnM4u c20zA1U+d9GPS2AOKlWaKLm2aOwuA7fAb0cuEbo5N/SFuDa2xCbZ6B0sqrZKd8RyTzgn v1jo2k0xZUUQHZe1SosCT/IQbmBweTh7qFzRQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=EiaIrvMZjFOPA8b72IZKfyisnwHaFkt/QMABI+e1bNHEt/JdyUDxlLasaBcIGDfwOp +5Cq5nNL3M55brdlpnLMYMfleMdNKq8oerjhhwAWmBnVwIDCjPHcMoGtNT1GD2cRjpIM MBgXmBT/5iKcy2/7WjBCgBurXeZ9mbZJhTWhQ= MIME-Version: 1.0 Received: by 10.229.98.131 with SMTP id q3mr21195392qcn.236.1294772731183; Tue, 11 Jan 2011 11:05:31 -0800 (PST) Sender: kylo.ginsberg@gmail.com Received: by 10.229.136.7 with HTTP; Tue, 11 Jan 2011 11:05:31 -0800 (PST) In-Reply-To: References: Date: Tue, 11 Jan 2011 11:05:31 -0800 X-Google-Sender-Auth: uWQbKyNGeNeLV76To-xbIZRQ_eY Message-ID: Subject: Re: Can I commit under a different user name? From: Kylo Ginsberg To: Andy Levy Cc: NN Ott , users@subversion.apache.org Content-Type: multipart/alternative; boundary=0016367f9c0ab503a7049996c4ff --0016367f9c0ab503a7049996c4ff Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 11, 2011 at 9:50 AM, Andy Levy wrote: > On Tue, Jan 11, 2011 at 12:42, NN Ott 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 --0016367f9c0ab503a7049996c4ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Jan 11, 2011 at 9:50 AM, Andy Le= vy <andy.levy@g= mail.com> wrote:
On Tue, Jan 11, 2011 at 12:42, NN Ott <= ;nonot100@gmail.com> wrote: > Hi all,
> If UserA checks out a working copy on to his machine, can UserB walk u= p to
> that machine and the commit changes under his own credentials?
> Would seem=A0possible, but just wanted to double check if there are an= y pit
> falls.
> Thanks

Credentials are cached in the user's home directory (~/.sub= version,
%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 a= ll 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
--0016367f9c0ab503a7049996c4ff--