Killhippie
Senior Member
I'm not sure Netgear will continue, I fear it was to placate a bug in the older version rather than bring a 10 year old SSL library (think it ten years old could be wrong) up to date. Time will tell. Also I cant believe they could not have dropped the latest version 1.02j (September release) into the latest firmware as the original vulnerability reported for OpenSSL was out there for 6 months (May 2016 was when I saw it reported in The register) unfixed in this and many other routers. Mind you a few users on twitter did name and shame netgear over its use of a very old version.Asus started updating it regularly about a year ago. If Netgear also starts following, then hopefully it will drive the rest of the herd to also follow in what should be a no-brainer (those OpenSSL updates are 100% backward compatible, and take about 10 minutes of development time to accomplish). The biggest hurdle is that initial update where you have to jump from whichever prehistoric branch you were using into either the latest 1.0.x branch (which is mostly straightforward if going from 1.0.0 to 1.0.2 - it's a drop in repalcement), or the newer 1.1.x branch (which might require some changes).
Now that manufacturers are starting to use OpenSSL for VPN purposes, having a secure version of OpenSSL is much more important than in the past, where it mostly handled https access to the webui within your LAN.