Hi again,
Turns out that this problem may (also?) be related to OpenSSL,
although again, nothing changed in regards to the SSL setup - but the
error is one that has ties to OpenSSL. I'm able to checkout
subfolders of our main project, but not the whole thing - other folks
have had similar problems, but the info I found on their issues ended
up being related to them updating OpenSSL to 0.9.8. The fix was
downgrading to 0.9.7 - I already have 0.9.7i.
As I work for a developer/publisher, I'd be happy to send a bunch of
OS X software to anyone that can save me from an all-nighter... not
that there's much information on the problem to go though - Google
doesn't turn up more than 2 or 3 pages depending on the query. =)
Thanks as always,
*justin
On Sep 27, 2006, at 6:09 PM, Justin wrote:
> Hi listers,
>
> Also FWIW, attempting to checkout another "test" project that only
> has four tiny tiny text files in it, works perfectly. It's just the
> main, big project that I receive the error below with.
>
> Thanks,
>
> *justin
>
> On Sep 27, 2006, at 5:51 PM, Samay wrote:
>
>> are u able to access https://ip.ad.dr.ess/pathtorepo/ through your
>> web browser ... whats the error there? then try https://
>> ip.ad.dr.ess/somelocal.file/ via ur web browser? do both work?
>>
>>
>> ----- Original Message ----- From: "Justin" <justin@hush.cc>
>> To: <users@subversion.tigris.org>
>> Cc: "Garrett Rooney" <rooneg@electricjellyfish.net>
>> Sent: Thursday, September 28, 2006 7:31 AM
>> Subject: Re: Help! REPORT fail & SSL error... UPDATE
>>
>>
>>> Hi Garrett,
>>>
>>> Trying it locally (using https://127.0.0.1/pathToRepository)
>>> results in the same error message actually! I'm thinking about
>>> recreating the self-signed certificate in the meantime, while I
>>> wait to see if anyone else has some input on the issue...
>>>
>>> Thanks a ton!
>>>
>>> *justin
>>>
>>>
>>> On Sep 27, 2006, at 5:20 PM, Garrett Rooney wrote:
>>>
>>>> On 9/27/06, Justin <justin@hush.cc> wrote:
>>>>> Hey again everyone,
>>>>>
>>>>> Turns out one of our devs used SubVersion 1.4.0 on our 1.3.latest
>>>>> server. So, updated the server to 1.4.0 and the clients expecting
>>>>> things to work... while the error I'm getting is now smaller, this
>>>>> part of the error still exists:
>>>>>
>>>>> svn: REPORT request failed on '/svn/!svn/vcc/default'
>>>>> svn: REPORT of '/svn/!svn/vcc/default': Could not read response
>>>>> body:
>>>>> SSL error: decryption failed or bad record mac (https://
>>>>> my.ip.goes.here)
>>>>>
>>>>> I'm seriously running into a lack of information on this error,
>>>>> despite people reporting it. Does anyone have any ideas? =
>>>>> ( I'm
>>>>> gearing up for an all-nighter here because I have to have this
>>>>> working...
>>>>
>>>> If I had to guess I'd say you should start looking for something
>>>> between the client and the server that's causing problems. Does
>>>> this
>>>> happen if you run the command right on the server, not going
>>>> over the
>>>> network at all?
>>>>
>>>> -garrett
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>> For additional commands, e-mail: users-help@subversion.tigris.org
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 28 01:32:59 2006