You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andrew Sasak <an...@gmail.com> on 2008/07/15 02:18:55 UTC
auth-access
For an unknown reason, our svn+ssh server will not allow 1.5 clients
to access the log. (Previous version clients work fine). We are using
path passed permissions in an authz file specified in svnserve.conf.
At the suggestion of somebody else on the list I experimented and
found that setting auth-access = write fixes the problem. (Since this
is the default, why is this necessary? Is this a bug?) What effect
does auth-access = write have when using the path based permissions?
Does it set the default permissions, which can be overridden in the
authz file with "* = "? Or does it override the authz file?
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: auth-access
Posted by Andrew Sasak <an...@gmail.com>.
I've been doing more testing and found that I was wrong, the
auth-access, doesn't seem to fix the problem running log after all,
and the newline at the end of the authz file doesn't help either. The
only sure way I've been able to fix this is to add * = r to the end of
the authz file. This is not necessary using a 1.4 client. Without
changing the authz file, with the 1.5 client I get a list of every
revision with no author or log entry when I use the root repository
path. If I attempt to get the log of the trunk I get "svn: Item is not
readable"
On Mon, Jul 14, 2008 at 10:31 PM, Andrew Sasak <an...@gmail.com> wrote:
> I reverted my svnserve.conf so that the auth-access line was commented
> out again, and added a newline to the end of my authz file, and log
> works like this as well.
>
> On Mon, Jul 14, 2008 at 10:18 PM, Andrew Sasak <an...@gmail.com> wrote:
>> For an unknown reason, our svn+ssh server will not allow 1.5 clients
>> to access the log. (Previous version clients work fine). We are using
>> path passed permissions in an authz file specified in svnserve.conf.
>> At the suggestion of somebody else on the list I experimented and
>> found that setting auth-access = write fixes the problem. (Since this
>> is the default, why is this necessary? Is this a bug?) What effect
>> does auth-access = write have when using the path based permissions?
>> Does it set the default permissions, which can be overridden in the
>> authz file with "* = "? Or does it override the authz file?
>>
>> Andrew
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: auth-access
Posted by Andrew Sasak <an...@gmail.com>.
I reverted my svnserve.conf so that the auth-access line was commented
out again, and added a newline to the end of my authz file, and log
works like this as well.
On Mon, Jul 14, 2008 at 10:18 PM, Andrew Sasak <an...@gmail.com> wrote:
> For an unknown reason, our svn+ssh server will not allow 1.5 clients
> to access the log. (Previous version clients work fine). We are using
> path passed permissions in an authz file specified in svnserve.conf.
> At the suggestion of somebody else on the list I experimented and
> found that setting auth-access = write fixes the problem. (Since this
> is the default, why is this necessary? Is this a bug?) What effect
> does auth-access = write have when using the path based permissions?
> Does it set the default permissions, which can be overridden in the
> authz file with "* = "? Or does it override the authz file?
>
> Andrew
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org