<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:"MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:"Courier New";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have a feeling that there is a bug in the NSS DH code. I’m getting almost the same error (in my case, the last message is “NSS: slot for DH key gen is NULL” instead of your “NSS: DH private key creation failed”). In my case, the mere fact that I have a certificate in the database triggers this error.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I posted the full log with plutodebug=all a couple days ago, but so far haven’t gotten a response.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> users-bounces@openswan.org [mailto:users-bounces@openswan.org] <b>On Behalf Of </b>Richard Pickett<br><b>Sent:</b> Sunday, July 24, 2011 8:30 PM<br><b>To:</b> Openswan Users<br><b>Subject:</b> [Openswan Users] nss DH woes<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Still plunking around trying to get certs to work on openswan. Got them imported into nss just fine, and it reports in the log that it loads them correctly. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>But when the first client connects, here's what hits the logs (notice the last line):<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: ignoring unknown Vendor ID payload [16f6ca16e4a4066d83821a0f0aeaa862]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] method set to=106 <o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] method set to=108 <o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: received Vendor ID payload [RFC 3947] method set to=109 <o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: ignoring Vendor ID payload [FRAGMENTATION 80000000]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: received Vendor ID payload [Dead Peer Detection]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: ignoring unknown Vendor ID payload [f14b94b7bff1fef02773b8c49feded26]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: ignoring unknown Vendor ID payload [166f932d55eb64d8e4df4fd37e2313f0d0fd8451]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: ignoring unknown Vendor ID payload [8404adf9cda05760b2ca292e4bff537b]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: packet from <a href="http://74.137.71.67:42600">74.137.71.67:42600</a>: received Vendor ID payload [Cisco-Unity]<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: "mobileaegisclient"[1] 74.137.71.67 #1: responding to Main Mode from unknown peer 74.137.71.67<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: "mobileaegisclient"[1] 74.137.71.67 #1: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:44 vhost5 pluto[6039]: "mobileaegisclient"[1] 74.137.71.67 #1: STATE_MAIN_R1: sent MR1, expecting MI2<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:45 vhost5 pluto[6039]: "mobileaegisclient"[1] 74.137.71.67 #1: NAT-Traversal: Result using RFC 3947 (NAT-Traversal): peer is NATed<o:p></o:p></p></div><div><p class=MsoNormal>Jul 24 22:26:45 vhost5 pluto[6039]: NSS: DH private key creation failed<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>What would cause the NSS DH private key creation to fail? Is this a client config issue or server side?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks for all your help!<o:p></o:p></p></div></div></body></html>