On Mon, Jan 05, 2004 at 10:06:01AM -0600, Bruce Guenter wrote:
> Greetings.
>
> I am having problems with subversion and SSL. I am using subversion
> 0.35.1 on Gentoo, with neon 0.24.4 and openssl 0.9.6k. The specific
> error I am seeing is this:
>
> svn: REPORT request failed on '/repos/portage/!svn/vcc/default'
> svn: REPORT of '/repos/portage/!svn/vcc/default': Could not read
response body: SSL error: decryption failed or bad record mac (https://svn.futurequest.net)
>
> This happens during either update or checkout. It used to work, and now
> it doesn't, so obviously something has changed.
Did you upgrade any of the software components? What does error_log say
on the server when you trigger this error?
> The repository is
> *only* accessable via https. Other computers can access the same
> repository, and I myself can access the repository files directly with
> both Galeon(Mozilla) and wget. If I set up a SSH tunnel to anywhere
> (including localhost), and do a checkout through that tunnel, it works
> fine. That is:
> svn co https://svn.futurequest.net/repos/portage/
> doesn't work, but:
> ssh -L 443:svn.futurequest.net:443 -N root@localhost &
> svn co https://localhost/repos/portage/
> DOES work.
>
> Has anybody else seen this, or have another idea to try?
That's quite strange; there have been a few similar reports of strange
SSL errors like this though. I presume you are using httpd-2.0.48?
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 7 22:20:26 2004