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

Re: Authentication/authorization issues

From: <kfogel_at_collab.net>
Date: 2005-04-29 16:19:18 CEST

Please see

   http://subversion.tigris.org/mailing-list-guidelines.html#replying

for why it's not good to start a new subject by replying to an
existing thread:

   Don't start a new thread (subject) by replying to an existing
   post. Instead, start a fresh mail, and write out the list address
   by hand. If you reply to an existing post, your mailreader may
   include metadata that marks your post as a followup in that
   thread. Changing the Subject header is not enough to prevent this!
   Many mailreaders will still preserve enough metadata to put your
   post in the wrong thread. If this happens, not only will some
   people not see your post (because they're ignoring that thread),
   but people who are reading the thread will waste their time with
   your off-topic post. The safest way to avoid this is to never use
   "reply" to start a new topic.

Thank you,
-Karl

"Gino Marckx" <dev@xodiac.be> writes:
> Hi there,
>
> 1. I have a mixed authentication and anonymous access setup for my
> Subversion installation and wanted to do the following for the test
> repository (which everybody can use to fool around with and get acquainted
> with Subversion in our company).
> So it is obvious that everybody has got write access, so the following
> line is added to the [test:/] section of my subversion access policy file:
>
> * = rw
>
> Now, for obvious reasons, locking cannot be used. So I added the
> following line to the section for the developers to be able to test
> locking when they wanted to:
>
> @developers = rw
>
> Apparently this does not work. Apache always seems to take the anonymous
> account in this case, and I get the message:
>
> svn: Lock request failed: 401 Authorization Required
>
> Is there any way to do what I want to do? Because I don't want to specify
> all non-developer users in the subversion access policy file...
>
> 2. Another thing. I think it would be very useful to be able to refer to
> user groups when specifying other users. E.g. like in the following
> example:
>
> admins = admin1, admin2
> developers = @admins, developer1, developer2, ...
>
> 3. Currently it is not possible to automatically secure (write lock) all
> tags. If it would be possible to specify something like:
>
> [test:/tags/*]
> * = r
>
> Then this would automatically be the case.
>
> Regards,
> Gino.
>
>
> ---------------------------------------------------------------------
> 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 Fri Apr 29 16:52:30 2005

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