Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 2 Oct 2012 14:35:25 +0200
From: Stefan Sperling <stsp@elego.de>
To: Nico Kadel-Garcia <nkadel@gmail.com>
Cc: david fasani <david-fasani@sab2i.com>, users@subversion.apache.org
Subject: Re: path-based authorization, users an groups synchronisation
 between master and slave
Message-ID: <20121002123525.GH16802@ted.stsp.name>
Mail-Followup-To: Nico Kadel-Garcia <nkadel@gmail.com>,
	david fasani <david-fasani@sab2i.com>, users@subversion.apache.org
References: <506AAC7A.8060906@sab2i.com>
 <20121002114859.GF16802@ted.stsp.name>
 <CAOCN9rz1niZhaaU8+VAj=J6t70GHdY9pNESyLCm2icKQVUZXCg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAOCN9rz1niZhaaU8+VAj=J6t70GHdY9pNESyLCm2icKQVUZXCg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Tue, Oct 02, 2012 at 08:01:30AM -0400, Nico Kadel-Garcia wrote:
> There are also some approaches that can help rigorously manage such
> configurations. I long for some Subversion developer to write
> something like the "gitosis" tool, which manages SSH keys for git's
> SSH based access, and which could use a Subversion repository to
> manage SSH keys for other Subversion repositories. It would make my
> preferred use of svn+ssh much easier.

s/Subversion developer/developer/ :)

While I agree that such a tool would be useful, it doesn't have to be
part of Subversion's core offering. It's probably easier to maintain
something like this as a separate project.