Reuben Sivan wrote:
> I recently configured our svn server to https-only.
>
> My Windows-based clients (both tortoise and the svn command line) work
> fine
> with that, however my Linux-based svn client does not work:
>
> > svn co https://myserver/... (from Linux)
> Unrecognized URL scheme 'https://myserver/...'
>
> > svn --version (on windows)
> * ra_dav...
> - handles http...
> - handles https...
>
> > svn --version (on Linux)
> * ra_dav...
> - handles http...
> (no https)
>
> Does anyone know how to configure the client so it will associate ra_dav
> with https as well as http?
From Subversion's INSTALL file:
The Neon library has support for SSL encryption by relying on the
OpenSSL library. When Neon is created with this dependency, then
the Subversion client inherits the ability to support SSL
connections. Neon also has support for sending compressed data
using the zlib library which a Subversion client can take
advantage of.
On Unix systems, if you are building neon as part of the Subversion
build process (as described in section I.4 above), you can pass flags
to Subversion's "./configure", and they will be passed on to neon's
"./configure". You need OpenSSL installed on your system, and you
must add "--with-ssl" as a "./configure" parameter. If your OpenSSL
installation is hard for Neon to find, you may need to use
"--with-libs=/path/to/lib" in addition. In particular, on Red Hat
(but not Fedora Core) it is necessary to specify
"--with-libs=/usr/kerberos" for OpenSSL to be found. The zlib library
is included in Neon by default, but you can also specify a path to the
library using "--with-libs". Consult the Neon documentation for more
information on how to use these parameters and versions of libraries
you need.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 11 00:50:50 2005