there is also nothing pertaining to this in the apache error logs on the
server side. Also I cannot telnet to the server on port 443. Does that
mean apache is not listening on that port?
thanks for all the responses....
On 10/9/07, Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
>
> He asked for https access, not unencrypted svnserve access...
>
> On Oct 9, 2007, at 01:11, ratnavel ps wrote:
>
> > Its pretty simple
> >
> > Open your dos prompt or the terminal window(In which system the
> > Subversion repository is) Type "svnserve -d -r repopath"
> >
> > You'll be able to connect.
> >
> > Regards,
> > ratnavel
> >
> > On 10/9/07, ion <gargolite@gmail.com> wrote:
> > thank you very much for all of your help.
> >
> > I configured apache httpd.conf with your example as a guide and it
> > started correctly, I think...
> > does svn on the server side have to be configured with the ability
> > to handle the https scheme?
> > my client is able to handle the https scheme, but when I try to
> > access the repo, I get the following:
> >
> > svn: PROPFIND request failed on '/svn/repo1'
> > svn: PROPFIND of '/svn/repo1': could not connect to server
> > ( https://server)
> >
> > any help or pointers will be appreciated
> >
> > On 10/4/07, Toby Thain < toby@smartgames.ca> wrote:
> > On 4-Oct-07, at 5:30 PM, ion wrote:
> >
> > >
> > > I've been wracking my head with this for weeks, and no amount of
> > > googling helped me.
> > >
> > > Has anyone here set up subversion, with a mostly standard apache2
> > > installation doing SSL encryption?
> > >
> > > I have subversion 1.4.5, apache 2.2.4 and openssl 0.9.8e installed,
> > > but I cannot figure out how to make them work together. I could be
> > > retarded.
> > >
> > > apache is installed in /usr/local/apache2, a very standard build
> > > from source, with mod_dav_svn and mod_authz_svn loading at startup.
> > >
> > > subversion and apache work together, I access my repositories
> > > through http://server/svn/repo . But I need it to run with https.
> > >
> > > Surely someone here has a similar set up and was successful
> > > configuring SSL to work with subversion, to the point of being able
> > > to relay how it was done.
> >
> > Have done this many times, on Linux and Solaris. The Svn Apache
> > modules don't care whether you're using SSL or not. The following is
> > extracted from my Apache config on Gentoo Linux. It assumes you have
> > built and installed the Apache modules for Subversion. Good
> > instructions for doing this are part of the Subversion source
> > distribution.
> >
> > # these are actually buried in /etc/apache2/modules.d/
> > 47_mod_dav_svn.conf
> > LoadModule dav_svn_module modules/mod_dav_svn.so
> > LoadModule authz_svn_module modules/mod_authz_svn.so
> >
> > <VirtualHost *:443>
> > ServerName DOMAIN.com
> > ErrorLog /var/www/logs/error-ssl.log
> > CustomLog /var/www/logs/access-ssl.log combined
> >
> > SSLEngine on
> > SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:
> > +SSLv2:+EXP:+eNULL
> > SSLCertificateFile conf/ssl/server.crt
> > SSLCertificateKeyFile conf/ssl/server.key
> >
> > <Location /svn>
> > DAV svn
> > SVNParentPath /var/svn # individual repos under here
> > # AuthzSVNAccessFile /var/svn/policy # if you wish
> >
> > Order allow,deny
> > Allow from all
> >
> > # example authentication setup
> > Require valid-user
> > AuthType Basic
> > AuthName "Subversion repository"
> > AuthUserFile /var/svn/htpasswd
> > Satisfy Any
> > </Location>
> > </VirtualHost>
> >
> > The trickiest part is creating the SSL cert and key (server.crt,
> > server.key ). I set up my own certifying authority (CA) according to
> > this recipe:
> > http://www.debian-administration.org/articles/284
>
>
--
http://www.myspace.com/acrylickalchemical
Received on Tue Oct 9 15:06:24 2007