On 12/15/06, Thomas Harold <tgh@tgharold.com> wrote:
>
> According to what I've read, when using HTTP, FILE, or SVN+SSH methods
> to access the repository, the conf/svnserve.conf file isn't used. So
> SVN+SSH users either have all or none access to the repository and you
> have to resort to hook scripts?
>
Nope, that is wrong. svn+ssh uses svnserve and therefore uses
conf/svnserve.conf and the authz settings that can go along with it.
> ...
>
> What I may do for some of the instances (where only a single user needs
> read/write access) is to give the user write permissions to the folders
> and only grant read permissions to the group (and no permissions for
> "other/world").
>
> Which gives me an idea. (Chapter 6 in the SVN Book at red-bean.com.) I
> can setup a central user account for a repository, have the users
> authenticate using public key pairs and then set the --tunnel-user=harry
> option in the authorized_keys file.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
Mark
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 16 07:18:37 2006