The developers have access to the server with any ssh client.
Thanks a lot for answering my question.
GM
On Thu, Apr 9, 2009 at 12:19 PM, Andy Levy <andy.levy_at_gmail.com> wrote:
> On Thu, Apr 9, 2009 at 10:35, Gerard Marcel <men.makaron_at_gmail.com> wrote:
> > Yes, and that is where I am trying to enforce the same file/directory
> > permissions as on https. I am not clear on what to use to get that
> effect.
> > I tried the included commit-access-control.pl, but it did not work.
>
> There is no security when using file:///. You can implement a hook
> script, but nothing will stop users from bypassing it.
>
> If you already have Apache working, why do you need file:/// at all?
>
> > On Thu, Apr 9, 2009 at 6:30 AM, Andy Levy <andy.levy_at_gmail.com> wrote:
> >>
> >> On Thu, Apr 9, 2009 at 00:06, Gerard Marcel <men.makaron_at_gmail.com>
> wrote:
> >> > I have setup permission in svn using mod_authz from https and that
> works
> >> > fine. Now while on cli I need to have the same permission for users
> >> > using
> >> > the svn command. I tried the commit-access-control.pl, but it does
> not
> >> > work
> >> > at all. Can someone provide some pointers?
> >>
> >> No matter what client you use, if you've implemented security at the
> >> server end, it'll be enforced.
> >>
> >> Do you have people accessing the repository via file:/// as well as
> https?
> >
> >
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1615859
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-09 21:37:44 CEST