I may have already stated this, but the way the build works
really sucks. Running configure on AIX powerpc would take
15 to 30 minutes.
Each time, determining whether my version of sed truncates
characters, the name of my default executable created by the
linker, etc. And, when things
So I guess the problem is this specific client certificate
though I still do not know what specifically.
Try using that cert on one of the machines with the 0.9.8g openSSL to
verify if it is that cert. You'll have to make sure you have both the
private and public key to do the
Hi all,
I'm new to subversion. I used CVSNT before.
Because a single svn commit will result in a whole new
revision tree, so currently I commit all changes once per day
after work (to avoid too many revisions because of my old CVS habit).
There's no particular reason to do that.
Can you try some tests without svn, for instance set up
apache to serve a simple static page protected by client cert
authentication, and try to access that with that cert using
openssl 0.9.8g vs. 0.9.8k?
Or try to build an svn client on your new machine with
openssl 0.9.8g instead of
One Thing of note that I forgot in my initial post and that
was partially mentioned by Johan:
Can you try some tests without svn, for instance set up apache to
serve a simple static page protected by client cert authentication,
and try to access that with that cert using openssl
