Since it's an open source project in which anyone can commit to the repository anytime, it's not possible to add each and every user as a system user. Instead, we're using Plone to write user information on the htaccess-style file that Subversion reads.
However, I guess I'm going to use your strategy on another server that is not wide open to commits, looks more than enough. Anyway, an Apache2 port wouldn't be a bad idea... I'll study some more and try to work on that on the near future. On 2/7/06, Joachim Schipper <[EMAIL PROTECTED]> wrote: > > On Tue, Feb 07, 2006 at 09:26:31PM -0200, Felipe Scarel wrote: > > Sure OpenBSD's modified Apache 1.3 is way more secure than most stuff > out > > there, and is working great. > > > > However, the Subversion versioning control system (which my project > uses) > > demands Apache2 in order to do DAV checkouts and commits, better > > authentication and more. So, my only choice was to manually install > Apache2 > > and compile mod_dav_svn.so in order to use these features in OpenBSD. No > big > > deal, but I would surely appreciate a port for Apache2, it would have > made > > my life much easier. > > > > Anyway, I agree with the other guys: no way Apache2 will make it to the > base > > system, its license is a major issue against that. > > I don't know about you, but I had the same svn-over-apache-2 setup. I > switched to svn+ssh, and all seems well. It has the added advantage of > taking version control further away from my very untrusted web scripts > and somewhat untrusted web server. > > sshd is a trusted component, at least in the sense that anyone who can > break that essentially owns the system. > > Joachim > > -- Felipe Brant Scarel PATUX/OpenBSD Project Leader (http://www.patux.cic.unb.br)
