pcp
[Top] [All Lists]

Re: [pcp] qa/713 certificate issue

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] qa/713 certificate issue
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 1 Apr 2013 21:10:50 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5154CE91.1070506@xxxxxxxxxxxxxxxx>
References: <5154CA71.3080200@xxxxxxxxxxxxxxxx> <5154CE91.1070506@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: DkcmDs2XLVZ1mHbWznrkSQWh4s5NmA==
Thread-topic: qa/713 certificate issue

----- Original Message -----
> Apologies ... I did not check the script and misread the output.
> 
> The issue really appears to be the "Peer's Certificate issuer is not
> recognized" error ... which is also seen in QA/712.
> 

These tests generate a self-signed certificate for use to validate
the SSL connections (so the certificate issuer is the qa host).
The qa/common.secure nss_setup_certificates function does this bit
fwiw.

> What am I doing wrong here?

Not clear, as the above certainly appears to be accepted on my setup
(nss-3.13.6-2).  Check the results of the nss_subject_name function
in common.secure might be a starting point, as this drives $certdomain
used later on (712.full should have greater detail).

cheers.

--
Nathan

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