Invalid certificate error
Jonathan Byrne <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <[email protected]> |
I just installed current-20011126 and made a self-signed
certificate as outlined in docs/encryption.txt.
In that document it is stated about 2.7 clients that
"I _think_ for them we'll need a true CA cert and signed cert."
I'm running Red Hat 7.2 with up2date-2.7.2-7.x.6 and
get an invalid client certificate error when I run
up2date aimed at my machine.
I have tried both the self-signed cert alone, and
catting it together with the Red Hat cert as
mentioned in encryption.txt, and both get this
error.
Has anyone gotten around this, or is it that case that
a real certificate is in fact required? If so, I'll look at
downgrading to a 2.5 client and see how that goes.
Typical output:
From stunnel:
Nov 28 18:38:39 yamame stunnel[16370]: 8000 connected from 203.216.0.50:45013
Nov 28 18:38:39 yamame stunnel[16370]: SSL_accept: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
From current:
client_address ('127.0.0.1', 44983)
command POST
path https://yamame.gol.ad.jp/XMLRPC
headers Host: yamame.gol.ad.jp
User-Agent: xmlrpclib.py/$Revision: 1.41 $
Content-Type: text/xml
X-Client-Version: 1
Content-Length: 2103
X-Info: XML-RPC Processor (C) Red Hat, Inc ($Revision: 1.30 $)
TIA,
Jonathan