pcp
[Top] [All Lists]

Re: [pcp] Secure connections writeup - please review

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] Secure connections writeup - please review
From: Dave Brolley <brolley@xxxxxxxxxx>
Date: Thu, 07 Feb 2013 10:36:34 -0500
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <946930016.871164.1360196530068.JavaMail.root@xxxxxxxxxx>
References: <946930016.871164.1360196530068.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
On 02/06/2013 07:22 PM, Nathan Scott wrote:
     * When using a certificate authority, it is sufficient for the
     clients to have the CA's signing certificate (as opposed to the
     server's actual certificate). This is the certificate that the
     CA uses to sign the certificates that it issues. If the client
     has the CA's signing certificate then it also trusts any
     certificates which are signed using that certificate. In this
     way, when the server's certificate expires, and it obtains a new
     certificate from the CA, the new certificate will be
     automatically trusted by clients without having to obtain a new
     certificate from the server.
Ah, that makes alot of sense.  Where would the client look to find
the CA's certificates?  I see there's an /etc/pki/nssdb that ships
with nspr, but it appears to be empty (no certs at all, according
to certutil -L).  Are they installed somewhere else?

I would assume that one would get the signing certificate from the CA itself. I don't know for sure. The systemtap compile-server does not use certificates from a CA. It uses its own self-signed certificates.

Dave

<Prev in Thread] Current Thread [Next in Thread>