<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: hp blade server in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/hp-blade-server/m-p/7041948#M21614</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Greetings!&lt;BR /&gt;Hope below answers your question - "How the client knows the SSL key and SSL certificate??"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;When the client is verifying a certificate, there are three possibilities:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The certificate is signed by a CA that the client already trusts (and for which it knows the public key). In this case the client treats the certificate as valid.&lt;/LI&gt;&lt;LI&gt;The certificate is signed by a CA about which the client has no knowledge at all. In this case the client treats the certificate as invalid (and the browser will likely display a warning message instead of loading the page).&lt;/LI&gt;&lt;LI&gt;The certificate is signed by a CA that the client doesn't know, but which has a certificate that is signed by a CA that the client&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;does&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;know. (In this case the server must usually send both its own certificate, and the certificate of the CA - called the "intermediate CA" - that signed its certificate). Since the intermediate CA's certificate is signed by a CA that the client already trusts, it knows can trust it, and since the server's certificate is signed by the intermediate CA, the client knows it can trust it too.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 10 Apr 2019 23:10:25 GMT</pubDate>
    <dc:creator>Guru_Verma</dc:creator>
    <dc:date>2019-04-10T23:10:25Z</dc:date>
    <item>
      <title>hp blade server</title>
      <link>https://community.hpe.com/t5/bladesystem-general/hp-blade-server/m-p/7041198#M21608</link>
      <description>&lt;P&gt;During locfg.pl execution in ubuntu 16.04 how this perl script get the SSL key and certificate file.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically I want to execute&amp;nbsp;&lt;/P&gt;&lt;P&gt;locfg.pl -f Insert_Virtual_Media.xml -u user -p pass -s IP_of_ILO&lt;/P&gt;&lt;P&gt;But the locfg.pl script gives failure during the creation of socket. I.e., due to the execution of below line.&amp;nbsp;&lt;/P&gt;&lt;P&gt;$socket = IO::Socket::SSL-&amp;gt;new(PeerAddr =&amp;gt; $server) || die $ConnectionErrorMessage;&lt;/P&gt;&lt;P&gt;The exact error at the client is: "ERROR: SSL connection error."&lt;/P&gt;&lt;P&gt;How the client knows the SSL key and SSL certificate??&lt;/P&gt;&lt;P&gt;Kindly let me know.&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 06:15:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/hp-blade-server/m-p/7041198#M21608</guid>
      <dc:creator>priyotoshtsp</dc:creator>
      <dc:date>2019-04-05T06:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: hp blade server</title>
      <link>https://community.hpe.com/t5/bladesystem-general/hp-blade-server/m-p/7041948#M21614</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Greetings!&lt;BR /&gt;Hope below answers your question - "How the client knows the SSL key and SSL certificate??"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;When the client is verifying a certificate, there are three possibilities:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The certificate is signed by a CA that the client already trusts (and for which it knows the public key). In this case the client treats the certificate as valid.&lt;/LI&gt;&lt;LI&gt;The certificate is signed by a CA about which the client has no knowledge at all. In this case the client treats the certificate as invalid (and the browser will likely display a warning message instead of loading the page).&lt;/LI&gt;&lt;LI&gt;The certificate is signed by a CA that the client doesn't know, but which has a certificate that is signed by a CA that the client&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;does&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;know. (In this case the server must usually send both its own certificate, and the certificate of the CA - called the "intermediate CA" - that signed its certificate). Since the intermediate CA's certificate is signed by a CA that the client already trusts, it knows can trust it, and since the server's certificate is signed by the intermediate CA, the client knows it can trust it too.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2019 23:10:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/hp-blade-server/m-p/7041948#M21614</guid>
      <dc:creator>Guru_Verma</dc:creator>
      <dc:date>2019-04-10T23:10:25Z</dc:date>
    </item>
  </channel>
</rss>

