RE: SVN Query about granting access

From: karthik kg
Sent: Wednesday, 9 April 2014 13:17 PM

        Hi Geoff,
        
        
        Apologies for replying to you. Please find my comments fro your queries below.

Replying directly to me is not a problem, really. What might be a problem is that I don't know as many of the answers as some of the other contributors to this mailing list.

        What result/message is the user actually seeing? I'm facing No ERROR at the moment.

Fair enough. From the description, that's what I'd expect.

        From what I'm seeing, you're trying to give that specific user read-only access, but they're getting read/write access. Yes, That's right. Even post changing the user settings, i m getting read-write access for that user(d389678)
        
        Some of my following queries are based on Windows and might not apply on your platform: Oh, anyway my platform is LINUX

I thought it might have been, but it's worth being sure. What specific version?

        Have they actually logged out and in again? Yes, Tried
        
        Have you restarted the httpd daemon after reconfiguring? (This shouldn't be necessary, but it could be worth a try.) Yes Tried.
        
        Do you grant global read/write access to that repository at all? Not sure, about this. Can you please tell me where this param value specified?

In your Subversion.conf file, there could be a line - most likely related to that repository - that says something like:

* = rw

Alternatively, you could have something like this to control global access:

[/]
* = rw

If there's a line like that in there, it's possible it will override the individual user settings. To make it global read-only, simply change it to:

* = r

Of course, I'm making a lot of assumptions here, but that's what works for us. We've been known to make specific repositories private in our configuration by saying (for that repository):

* =

I'm not totally convinced it will work, since the individual settings seem to override the global ones. More knowledgeable heads than mine might have more of a clue.

Having said all this, one has to ask if restricting that user's access is strictly necessary. Given that SVN logs all writes and changes and that everything can be reversed, is it really such a huge risk?

On the other hand, of course, there's the learning exercise for working out how to set the configuration file up.

Regards,

Geoff

-- 
Apologies for the auto-generated legal boilerplate added by our IT department:
- The contents of this email, and any attachments, are strictly private
and confidential.
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files.