I think I understand how I was wrong, most of the stuff I
work with negotiates the secure connection immediately,
such as web on 443 (https) and ldaps (667?). I see that
if there was a reqired interaction before switching over
into secure mode (which is TLS rather than SSL?) that it
might not be s
On Wed, Jun 23, 2004 at 07:47:35AM -0400, Charles Cranston wrote:
> It's not hard at all to use openssl s_client to try to
> make a connection and to see the certificate that is
> being presented by the server. If you use the -showcerts
> option it will even show the entire certificate chain being
It's not hard at all to use openssl s_client to try to
make a connection and to see the certificate that is
being presented by the server. If you use the -showcerts
option it will even show the entire certificate chain being
presented by the server, instead of just the end-user cert.
I have good l
Lutz Jaenicke wrote:
No. The problem is located in between the ears.
Ouch! But thanks for helping
I am most sorry, but your statement is wrong. This is not the
certificate used on the host in question. I just did connect to
You are, of course, correct. I was assured that the cert I was
given
