Firmware 4.3.3-6 Using Self Signed Cerificates with Serial Number "0"

Firmware 4.3.3-6 has an embedded Cerificate used for security.  PROBLEM: The NetGear Self Signed Certificate has a Serial Number of "00" (or "0").

If any other self signed certificate is used elsewhere a security issue is raised and systems begin to fail.  Our site was down most of a day until we accidentally found the problem.  And worst of all the firewall dropped WAN connection and would not link and of course no messages were broadcast.

To compound the fact Browsers did not want to connect to the Admin pages because the certificate was deemed bad with a "0" serial number.

IMO, NetGear Engineers "must" release a new firmware version with a non-zero self signed certificate.  I believe OpenSSL has a "x509" parameter that will generate a non-zero serial number.  Using a "0' serial number in a self signed certificate inside firmware is a disaster waiting to happen -- and in our case it did.

PLEASE release a new firmware with the appropriate fix for the "0" serial number ASAP.

Under the right conditions the Firewall will not accept WAN connections or browser connections and there are no error messages or logs or any indications of what happened.  We found the problem "by accident" after hours of running blind.  PLEASE eliminate this problem from ever possibly occuring in the future by using self signed certificates in firmware with a non-zero serial number.