<?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: Install new certificate on VOSS 9.2 in ExtremeSwitching (Other)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118691#M4254</link>
    <description>&lt;P&gt;Fabric Engine supports&amp;nbsp;&lt;SPAN&gt;SHA256 for certificates. It's just the CSR are SH1 based. If you generate a CSR you can load it to a computer where openssl is in place and expose the details like this&lt;BR /&gt;&lt;STRONG&gt;openssl req -noout -text -in switch-1.csr&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The CA sign the certificate and determinate which signing hashing will be used. By default is using OpenSSL&amp;nbsp;sha256WithRSAEncryption. Also here you can expose the details like this&lt;BR /&gt;&lt;STRONG&gt;openssl x509 -noout -text -in switch-1.pem&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I made a document describing all the certificate related topics on our Fabric Engine (attached).&lt;/P&gt;</description>
    <pubDate>Fri, 09 May 2025 06:23:35 GMT</pubDate>
    <dc:creator>Markus_Nikulski</dc:creator>
    <dc:date>2025-05-09T06:23:35Z</dc:date>
    <item>
      <title>Install new certificate on VOSS 9.2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118688#M4253</link>
      <description>&lt;P&gt;I am trying to install a new certificate on a VOSS 9.2 switch and I believe v9.1 onwards supports SHA256. When I use these commands to generate a CSR and sign it with our internal CA using OpenSSL, MS Edge displays an "unsupported certificate format" error, so I assume it's still SHA1.&lt;/P&gt;&lt;P&gt;Anyone any ideas if SHA256 is indeed supported in VOSS 9.2, or are there other commands ?&lt;/P&gt;&lt;P&gt;The commands I used are:&lt;/P&gt;&lt;P&gt;no certificate generate-keypair&lt;/P&gt;&lt;P&gt;certificate generate-keypair type rsa size 2048&lt;/P&gt;&lt;P&gt;show certificate key-name&lt;/P&gt;&lt;P&gt;certificate subject common-name TESTSWITCH&lt;BR /&gt;certificate subject e-mail ADMIN@ABC.COM&lt;BR /&gt;certificate subject unit IT&lt;BR /&gt;certificate subject organization ABC&lt;BR /&gt;certificate subject locality GLA&lt;BR /&gt;certificate subject country GB&lt;BR /&gt;certificate subject province NA&lt;BR /&gt;certificate subject-alternative-name dns TESTSWITCH&lt;BR /&gt;certificate subject-alternative-name dns TESTSWITCH@ABC.COM&lt;/P&gt;</description>
      <pubDate>Thu, 08 May 2025 07:12:28 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118688#M4253</guid>
      <dc:creator>dabbler</dc:creator>
      <dc:date>2025-05-08T07:12:28Z</dc:date>
    </item>
    <item>
      <title>Re: Install new certificate on VOSS 9.2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118691#M4254</link>
      <description>&lt;P&gt;Fabric Engine supports&amp;nbsp;&lt;SPAN&gt;SHA256 for certificates. It's just the CSR are SH1 based. If you generate a CSR you can load it to a computer where openssl is in place and expose the details like this&lt;BR /&gt;&lt;STRONG&gt;openssl req -noout -text -in switch-1.csr&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The CA sign the certificate and determinate which signing hashing will be used. By default is using OpenSSL&amp;nbsp;sha256WithRSAEncryption. Also here you can expose the details like this&lt;BR /&gt;&lt;STRONG&gt;openssl x509 -noout -text -in switch-1.pem&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I made a document describing all the certificate related topics on our Fabric Engine (attached).&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 06:23:35 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118691#M4254</guid>
      <dc:creator>Markus_Nikulski</dc:creator>
      <dc:date>2025-05-09T06:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: Install new certificate on VOSS 9.2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118694#M4255</link>
      <description>&lt;P&gt;Hi Markus,&lt;/P&gt;&lt;P&gt;Thanks a lot for the docs, I'll try again from scratch and see how it goes, but it looks like I was on the right track. Using Firefox works fine with the certs I generated, it's just MS Edge that displays this error. The cert and CA looks good, I can't see what&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dabbler_0-1746798462029.png" style="width: 400px;"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/8836i17334B7F6CF81B5A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dabbler_0-1746798462029.png" alt="dabbler_0-1746798462029.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Maybe going off topic here, but Wireshark displays this:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dabbler_1-1746798542467.png" style="width: 400px;"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/8837iC30EE3CA50A5832A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dabbler_1-1746798542467.png" alt="dabbler_1-1746798542467.png" /&gt;&lt;/span&gt;The root CA is installed OK, I can't see what the problem is. Our organisation uses MS Edge as standard, so I can't tell them to just use Firefox &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 13:50:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118694#M4255</guid>
      <dc:creator>dabbler</dc:creator>
      <dc:date>2025-05-09T13:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: Install new certificate on VOSS 9.2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118696#M4256</link>
      <description>&lt;P&gt;Please be aware that an MSFT computer has three certificate stores. And Firefox uses the one in addition.&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 06:13:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118696#M4256</guid>
      <dc:creator>Markus_Nikulski</dc:creator>
      <dc:date>2025-05-12T06:13:39Z</dc:date>
    </item>
    <item>
      <title>Re: Install new certificate on VOSS 9.2</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118697#M4257</link>
      <description>&lt;P&gt;That's right, we do have Microsoft PKI but are not using that just now. We are using an OpenSSL generated root certificate to directly sign the switch certificates. I added the root certificate into the trusted root CA store in Windows under the computer account and also into Firefox's root CA store.&lt;BR /&gt;When I double click the switch.crt file on my Windows machine, I can view it and it validates to the root no problem so I don't think it's the validation process, although feel free to correct me on that.&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 07:16:56 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/install-new-certificate-on-voss-9-2/m-p/118697#M4257</guid>
      <dc:creator>dabbler</dc:creator>
      <dc:date>2025-05-12T07:16:56Z</dc:date>
    </item>
  </channel>
</rss>

