[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xymon] sslcert
- To: xymon (at) xymon.com
- Subject: Re: [xymon] sslcert
- From: "Xymon User in Richmond" <hobbit (at) epperson.homelinux.net>
- Date: Thu, 20 Jan 2011 18:52:01 -0500
- Importance: Normal
- References: <1295462714.2946.8.camel (at) Nokia-N900> <2685F464D7BC7C4DA88845C97AEB5F533A9AEA37B1 (at) qtomaexmbm22.AD.QINTRA.COM> <4D374E08.8030908 (at) makelofine.org> <ihabli$op1$1 (at) voodoo.hswn.dk>
- User-agent: SquirrelMail/1.4.21-1.fc14
On Thu, January 20, 2011 17:06, Henrik Størner wrote:
> OK, so you have (at least) 7 SSL-enabled services running on one host.
> The effect of that is rather unpredictable - when doing the "sslcert"
> status, I didn't think that you would have one line in hosts.cfg with
> multiple (different) SSL certificates. So which of the 7 certificates
> will show up in the "sslcert" status is unpredictable.
>
I have hosts running both httpd ssl and imaps services, with separate
certs, and it reports both certs correctly. I don't know if it will
handle status correctly, though. The imaps certs are self-generated with
expirations years out. IIRC, it has gone yellow on the httpd certs at the
correct time. The https test precedes the imaps test on the hosts line,
and the certs are stacked in that order on the sslcert page.