Hi everyone!
I wanted to tell everyone my system is now fully up and running with all
components using 1.0.1e.
The only change needed was the static loading of mod_ssl in Apache HTTPD,
as well as using the static libraries for libssl and libcrypt; the other
thing I needed to do was a full
On Mon, February 18, 2013 3:04 am, Eisenacher, Patrick wrote:
Hi Joel,
Looks like your client doesn't trust the server's root CA certificate.
Try to invoke s_client with either the -CApath or the -CAfile option.
Thanks for your note.
The issue I have been reporting has never been on the
Thank you all for your kind help. I noticed the lack of the trace option
with 1.0.1e. Is there some way for me to check out a copy of 1.0.2
development, to see if it exhibits the same problem - and if it does, to
capture a trace?
I have not been able to progress much on this, because of other
Mr. Salz -
You bring up excellent points!
I must admit that since this is a personal server sitting in my home
(albeit used by my wife for consulting work of hers), I do allow for
contradictory goals to exist. Part of my desire is to avoid *known*
security vulnerabilities. As to the unknown ones
On Mon, February 18, 2013 3:04 am, Eisenacher, Patrick wrote:
Hi Joel,
Looks like your client doesn't trust the server's root CA certificate.
Try to invoke s_client with either the -CApath or the -CAfile option.
Thanks for your note.
The issue I have been reporting has never been on the
Here is the output from a machine connecting to my server, once with it
running 1.0.1c and also with it running 1.0.1e. I have spent hours trying
to work this issue. I have it down to this: I have a two bootable
partitions on my computer. The only relevant difference between them is
the first has
Here is the output from running an 'openssl s_client -debug' command (as
much verbosity as I could quickly find.) The key difference between the
two seems to be in the 1.0.1e case, there is this extra text at the end.
1.0.1c does not show this error.
13780:error:140790E5:SSL
