I found a reference to a problem with the same error message in the
archives of an openssl listserv, and one of the openssl developers
suggested reverting to openssl 0.9.7 from 0.9.8a.
Well, this seems to be a fix, for now.
I had an old version of the openssl port in an obsolete darwinports tree
on my machine and reinstalled openssl and dependencies up through
If you are having this SSL error, it is pretty confounding, because it
only occurs for large commits/copies. If you are using darwinports for the
install, I can send you the portfile for openssl 0.9.7e, which seems to
To conclude, this combination seems to be stable:
Edward D. Zaron
College of Oceanography and Atmospheric Science
Oregon State University
104 COAS Admin Bldg
Corvallis, OR 97331-5503
On Wed, 15 Mar 2006, Jonathan Williams wrote:
> Hi Ed!
> On Mar 15, 2006, at 5:30 PM, Ed Zaron wrote:
>> I am having the same problem described in a couple of archived posts from
>> last year. I wonder if there is any more information or a solution? The
>> error message is in the subject line.
>> I had never encountered this problem before, but I recently made some
>> upgrades using Darwinports:
>> (I am running Apple OS X 10.3.9; gcc 3.3 20030304)
> Just wanted to chime in and mention that I am having the exact same problem
> on Mac OS X 10.4.5 (intel) with all my packages built from Darwinports as
> I recently had an issue with Darwinports Apache having issues with loading
> both DP and Apple Kerberos libraries (detailed in this thread:
> http://mailman.mit.edu/pipermail/kerberos/2006-March/009406.html). I wonder
> if the issue is similar.
>> Also, I recently updated my self-signed certificate. I have a dynamic IP
>> address, which is usually unchanged, but whenever an extended power outage
>> occurred in my building, I would get a new IP address and have to switch
>> all of my working copies to point to the new repo address. This caused
>> problems with some windows svn clients, which blocked connections to my
>> https site because my actual IP address and hostname did not match what was
>> in my secure certificates.
> I wouldn't worry about this causing the problem.
> What I would suggest is that someone with a know good apache+ssl server
> contact Ed and/or myself to arrange to try our clients out on a large svn
> import to it. The process should be also done for our Apache SSL servers with
> a known good client. We need to figure out where the problem is originating.
> Any takers?
> Jonathan C. Williams
> Web Programmer
> Steinhardt School of Education
> email@example.com :: 212-998-5308
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Mar 17 02:55:47 2006