At 11:07 PM 11/20/00 +, you wrote:
There should be either a load of trusted certificates in a single file
or a directory containing them. If you are using client authentication
then it may try to read the whole lot in. If one is corrupt then this
could be a problem.
Actually now I look at
"Visionary Website Creations, Inc." wrote:
At 11:07 PM 11/20/00 +, you wrote:
There should be either a load of trusted certificates in a single file
or a directory containing them. If you are using client authentication
then it may try to read the whole lot in. If one is corrupt then
At 09:50 PM 11/17/00 +, you wrote:
"Visionary Website Creations, Inc." wrote:
Hi,
I chatted via IRC with a Thawte tech for about 3 hours. Unfortunately,
we're stumped.
Here's the problem:
I generated a csr for probrasive.com using SSLeay. While trying to install
the resulting
"Visionary Website Creations, Inc." wrote:
At 09:50 PM 11/17/00 +, you wrote:
"Visionary Website Creations, Inc." wrote:
Hi,
I chatted via IRC with a Thawte tech for about 3 hours. Unfortunately,
we're stumped.
Here's the problem:
I generated a csr for probrasive.com
At 04:57 PM 11/20/00 +, you wrote:
"Visionary Website Creations, Inc." wrote:
At 09:50 PM 11/17/00 +, you wrote:
"Visionary Website Creations, Inc." wrote:
Hi,
I chatted via IRC with a Thawte tech for about 3 hours. Unfortunately,
we're stumped.
Here's the problem:
"Visionary Website Creations, Inc." wrote:
What does this alleged certificate look like? Can you read it with
openssl x509 -in cert.pem
or does it give a similar error? Can you include the certificate file?
It doesn't contain anything confidential and it may be packaged in an
unusual
At 07:54 PM 11/20/00 +, you wrote:
Hmmm seems OK to me too. Is that the only certificate in the file?
I suppose it is possible that some other certificate it attempts to read
in somewhere is corrupt: check the trusted file or directory to see if
anything is wrong there.
Steve.
There is one
"Visionary Website Creations, Inc." wrote:
At 07:54 PM 11/20/00 +, you wrote:
Hmmm seems OK to me too. Is that the only certificate in the file?
I suppose it is possible that some other certificate it attempts to read
in somewhere is corrupt: check the trusted file or directory to see
