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

Re: Bug in authentication when working with "needs-lock"

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-11-26 18:33:34 CET

Actually, in trying to reproduce this error, I've discovered that user
'yosi' can't even 'svn lock' the file in the first place:

$ svn lock file -m "blahblah" --username yosi
Authentication realm: <svn://localhost:3690> My First Repository
Password for 'yosi':
subversion/svnserve/serve.c:1754: (apr_err=170001)
svn: Authorization failed

I think we should file this as a bug.

On 11/22/06, Froenchenko Leonid <gregor66@mail.ru> wrote:
> When performing commit against svnserve for file which being locked (and
> have svn:needs-lock), and user have write access only to affected
> directory (not repository root), commit is failed with:
>
> svn: Commit failed (details follow):
> svn: Authorization failed
>
> If lock removed before commit, everithing is fine.
>
> Setup:
> authz:
>
> [groups]
> g0=yosi
> g1=moshe
>
> [/]
> *=r
>
> [/trunk/dir0]
> @g0=rw
>
> [/trunk/dir1]
> @g1=rw
>
> When user "yosi" commits in dir0, error is happen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 26 18:33:59 2006

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