Date: Fri, 10 May 2002 12:22:12 -0500
From: Thaddeus Parkinson <[EMAIL PROTECTED]>
Well, OpenSSL 0.9.6d has definately made a difference, although I wouldn't
say anything has improved. I now receive a 'verify error:num=19:self
signed certificate in certificate chain'. I'm not sur
Raslin' Frazzlin' Hoogina Shoogina
I can't believe that. This whole time, I was trusting imtest. I feel so
cheated.
Sure thing, I punched open Pine, and it came up with a screen complaining
about not having the CA cert, but worked just fine. No errors in the
logs.
Actually, if it wasn't for
You know to be quite honest i get the same error message with mine no
matter what, self signed, etc.
But i'll be honest, it works JUST fine in Mutt, and Mulberry which are my
only SSL based applications i test it on.
Same error message as you, so i wouldnt worry as much about 'imtest'. It's
Well, OpenSSL 0.9.6d has definately made a difference, although I wouldn't
say anything has improved. I now receive a 'verify error:num=19:self
signed certificate in certificate chain'. I'm not sure if that's an
improvement or not, but it looks better. Apart from that, on the server
side, I now
Jason (and the rest of the Cyrusians out there),
Thanks for the suggestions. The new certs definately get me different
messages. Now I receive a 'verify error:num=27:certificate not trusted'
on the CA file. I think this might be a problem with imtest not trusting
the CA, anybody have any idea
On Thu, 9 May 2002, Thaddeus Parkinson wrote:
> Things that catch my eye are the lines complaining about no CA data, and
> then, obviously, the SSL3 alert write:fatal:unknown. I don't think
> they're inter-related, since a self-signed cert should be sufficient
> for testing. Is it possible tha
Alright, I'm breaking down and turning to you guys for help. I know, it's
not even about the latest cutting edge development branch but rather a
2.0.16 problem. My descendents will be cursed for generations to come
because of this, yet I have no one else to turn to. Please, loan me your
pity an
