NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
"Let's Encrypt" - has anyone tested on ReadyNAS?
Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting a certificate can be. Let’s Encrypt automates away all this pain and lets site operators turn on...
I agree its cool. FWIW, they will be an intermediate CA - the underlying root CA is IdenTrust - which already is an established root CA.
To test their client, you would need to manually integrate it into apache on the NAS. I haven't tried that. Also their client reconfigures your security settings to get an "A" on ssl-labs tests. Not sure if any of that will get in the way of the web ui or any apps.
One obvious issue for home users is that the DDNS provider owns the main domain name (and probably has a cert for it). I think the letsencrypt policies are still being worked out, but it might not be able to issue a certificate for xxx.mynetgear.com if Netgear already has a cert for mynetgear.com.
In addition, if you have more than one NAS (as I do), you likely have all of them them using the same domain name but using different ports. The deeper-dive video I watched said that they weren't sure if they could grant certs automatically to multiple servers sharing the same domain name. But you might be able to do that manually once you got a cert for the first machine. And they might be thinking about a cluster, not dedicated servers listening on different ports.
Anyway, its on my watch list, and if you know the answers on the policies/limitations please post them. My source was https://media.libreplanet.org/u/librepl ... s-encrypt/, it is about 7 weeks old.
To test their client, you would need to manually integrate it into apache on the NAS. I haven't tried that. Also their client reconfigures your security settings to get an "A" on ssl-labs tests. Not sure if any of that will get in the way of the web ui or any apps.
One obvious issue for home users is that the DDNS provider owns the main domain name (and probably has a cert for it). I think the letsencrypt policies are still being worked out, but it might not be able to issue a certificate for xxx.mynetgear.com if Netgear already has a cert for mynetgear.com.
In addition, if you have more than one NAS (as I do), you likely have all of them them using the same domain name but using different ports. The deeper-dive video I watched said that they weren't sure if they could grant certs automatically to multiple servers sharing the same domain name. But you might be able to do that manually once you got a cert for the first machine. And they might be thinking about a cluster, not dedicated servers listening on different ports.
Anyway, its on my watch list, and if you know the answers on the policies/limitations please post them. My source was https://media.libreplanet.org/u/librepl ... s-encrypt/, it is about 7 weeks old.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
