<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:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#44546A;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle24
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle25
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@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="#0563C1" vlink="#954F72"><div class=WordSection1><p><span style='color:#1F497D'>The importing of CA signed certificates-OMSA CLI feature is planned to deliver as part OMSA 8.1 release. <o:p></o:p></span></p><p><span style='color:#1F497D'>Regards<o:p></o:p></span></p><p><span style='color:#1F497D'>Vish Ponnuru.<o:p></o:p></span></p><p>-----Original Message-----<br>From: linux-poweredge-bounces-Lists On Behalf Of Stefan M. Radman<br>Sent: Saturday, October 18, 2014 4:25 AM<br>To: linux-poweredge-Lists<br>Subject: Re: [Linux-PowerEdge] OMSA 7.4.0 and sec_error_ca_cert_invalid on new CentOS6.5 install<br><br>Same seen with firefox 31.1.0 on RHEL 6.5 server<br><br>any solution appreciated<br><br>Thanks<br>Stefan<br><br>On Oct 17, 2014, at 5:42 PM, Shane Forsythe wrote:<br><br>&gt; The default install of firefox on any new centos machines is now invalidating the certificate with OMSA. I have found some documentation about updating the cert once you are logged in, but does anyone know of a way to update the cert from the command line?<br>&gt; <br>&gt; Does Dell have a ca.cert file we can import, or we have to use our own ca and self-signed keys?<br>&gt; <br>&gt; Thanks<br>&gt; Shane<br>&gt; <br>&gt; _______________________________________________<br>&gt; Linux-PowerEdge mailing list<br>&gt; <a href="mailto:Linux-PowerEdge@dell.com">Linux-PowerEdge@dell.com</a><br>&gt; <a href="https://lists.us.dell.com/mailman/listinfo/linux-poweredge">https://lists.us.dell.com/mailman/listinfo/linux-poweredge</a><br><br>_______________________________________________<br>Linux-PowerEdge mailing list<br><a href="mailto:Linux-PowerEdge@dell.com">Linux-PowerEdge@dell.com</a><br><a href="https://lists.us.dell.com/mailman/listinfo/linux-poweredge">https://lists.us.dell.com/mailman/listinfo/linux-poweredge</a><o:p></o:p></p></div></body></html>