<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>M4300 on shocksolution.com</title><link>https://shocksolution.com/tags/m4300/</link><description>Recent content in M4300 on shocksolution.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Apr 2020 03:50:18 +0000</lastBuildDate><atom:link href="https://shocksolution.com/tags/m4300/index.xml" rel="self" type="application/rss+xml"/><item><title>How to use SSL/TLS certificates on a Netgear M4200/4300 switch</title><link>https://shocksolution.com/posts/ssl-tls-certificates-netgear-m4200-4300-switch/</link><pubDate>Fri, 03 Apr 2020 03:50:18 +0000</pubDate><guid>https://shocksolution.com/posts/ssl-tls-certificates-netgear-m4200-4300-switch/</guid><description>&lt;p&gt;If you operate a Netgear switch in an environment that is subject to compliance requirements such as PCI or HIPAA, you are probably doing vulnerability scans, and the HTTP management interface of your switches will generate medium vulnerabilities (at least from Nessus):&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;SSL Self-Signed Certificate&lt;/em&gt;SSL Certificate Cannot Be Trusted* SSL Certificate Expiry&lt;/p&gt;&#10;&lt;p&gt;It &lt;strong&gt;IS&lt;/strong&gt; possible to use signed certificates to secure the HTTPS interface on a Netgear switch, but the process to do so is insanely obscure. I do not know how someone had time to figure this out! Apparently, even Netgear tech support didn&amp;rsquo;t have any idea.&lt;/p&gt;</description></item></channel></rss>