On Sat, 3 Apr 2004 16:49:18, Pierre THIERRY wrote: > > My expectation is that in most cases svnserve is used on conjunction > > with ssh or is started via inetd > > No, in the contrary, the SSH tunneling is more an option than the main > use case. Taken from the SVN website (http://subversion.tigris.org/)Â : > > "Subversion also offers a standalone server option using a custom > protocol (not everyone wants to run Apache 2.x). The standalone server > can run as an inetd service, or in daemon mode, and offers basic > authentication and authorization. It can also be tunnelled over ssh."
The documentation now at http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.serverconfig.choosing.recommendations recommends against SSH tunnelling, saying: "In general, the authors of this book recommend a vanilla svnserve installation for small teams just trying to get started with a Subversion server; it's the simplest to set up and has the fewest maintenance issues." It goes on to recommend using svnserve with SASL if encryption is required, instead of tunnelling with SSH which is "effectively the same as local users accessing via file://", which in turn is strongly discouraged. Roger -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
