[an error occurred while processing the directive]

	cosign-discuss at umich.edu
	general discussion of cosign development and deployment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Very weird errors

To: Brett Lomas <b.lomas@xxxxxxxxxxxxxx>
Subject: Re: Very weird errors
From: Phil Pishioneri <pgp@xxxxxxx>
Date: Sun, 03 Apr 2005 23:25:05 -0400
Cc: cosign-discuss <cosign-discuss@xxxxxxxxx>, Timothy Chaffe <t.chaffe@xxxxxxxxxxxxxx>
In-reply-to: <1112583352.4338.37.camel@brett.enarc.auckland.ac.nz>
References: <1112583352.4338.37.camel@brett.enarc.auckland.ac.nz>
User-agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317)

On 4/3/05 10:55 PM, Brett Lomas wrote:

When some of our webservers connect I get the following error:
Apr  4 14:09:40 cerberus2 cosignd[18631]: f_starttls: snet_starttls:
error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca

now normally i would attribute this to a CA not being installed on the
machine, but alas this is not the case. The web server's client
certificate details are:
...

and on the cosign server the following CA certs are installed (along with their hash values):

Not brilliant ideas, but...

The cosignd's CA is installed on the web server client? (And it wasn't upgraded to 1.1.1, and needs the path changed and hashing done?)

-Phil

Follow-Ups:
- Re: Very weird errors
  - From: Brett Lomas

References:
- Very weird errors
  - From: Brett Lomas

Prev by Date: Very weird errors
Next by Date: Re: Very weird errors
Previous by thread: Very weird errors
Next by thread: Re: Very weird errors
Index(es):
- Date
- Thread

[an error occurred while processing the directive]