You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Phil Crooker <Ph...@orix.com.au> on 2016/05/30 06:38:09 UTC
view log problem with path authorisation
I posted this query to the users list but had no response. To me, this is not behaviour I would expect.
Authenticated users with read or r/w authorisation are unable to view logs, eg:
# svn --username whatever --password xxxxx log svn://svn/repos/project/yada.txt
svn: Item is not readable
After authentication, users are able to check out files, etc, just not see the logs. For anyone to view logs, I must grant anonymous read access in authz and then it works:
[/]
* = r
I've seen this reported earlier but no answer:
http://svn.haxx.se/users/archive-2011-02/0141.shtml
http://stackoverflow.com/questions/6651997/svn-show-log-not-working
Is this a bug or is it expected behaviour?
thanks, Phil
--
This message from ORIX Australia might contain confidential and/or
privileged information. If you are not the intended recipient, any use,
disclosure or copying of this message (or of any attachments to it) is
not authorised.
If you have received this message in error, please notify the sender
immediately and delete the message and any attachments from your
system. Please inform the sender if you do not wish to receive future
communications by email.
The ORIX Australia Privacy Policy outlines what kinds of personal
information we collect and hold, how we collect and handle it and your
rights in regards to your personal information. Our Privacy Policy is
available on our website: http://www.orix.com.au .
We do not accept liability for any loss or damage caused by any computer
viruses or defects that may be transmitted with this message. We
recommend you carry out your own checks for viruses or defects.
Re: view log problem with path authorisation
Posted by Stefan Sperling <st...@elego.de>.
On Mon, May 30, 2016 at 06:38:09AM +0000, Phil Crooker wrote:
> I posted this query to the users list but had no response. To me, this is not behaviour I would expect.
Hi Phil,
please do not use the dev@ list as an escalation path for users@.
Some people are subscribed to both lists. Replying to your own thread
on the users@ list and mentioning the lack of responses should suffice.
Even if you do so a few times, it won't disturb anyone.
I'll try to find your post on users@ and reply there.
Thanks,
Stefan