NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
HTTPS, ReadyNAS Duo V2 and Chrome
I have been using my Duo V2 with chrome without any problems for sometime... I followed the examples about importing a certificate and all has been well for years. I have no problem with IE 11 but th...
To be very clear -
(a) The SHA256 change is certainly needed for PKI certs. Those certificates are verified with the certificate authority using the sha signature. SHA1 will not be strong enough for that relatively soon (due to dropping costs of cloud computing).
(b) But self-signed certificates (like all root certificates) aren't verified with the sha signature at all. Instead they are simply installed.
So changing the self-signed cert to SHA256 doesn't improve the security (e.g., make the units "more hackable").
Google is (for unknown reasons) choosing to needlessly apply the sha256 check with a self-signed cert. Going to sha256 in the NAS avoids the error message from Chrome, but that is all it does.
(a) The SHA256 change is certainly needed for PKI certs. Those certificates are verified with the certificate authority using the sha signature. SHA1 will not be strong enough for that relatively soon (due to dropping costs of cloud computing).
(b) But self-signed certificates (like all root certificates) aren't verified with the sha signature at all. Instead they are simply installed.
So changing the self-signed cert to SHA256 doesn't improve the security (e.g., make the units "more hackable").
Google is (for unknown reasons) choosing to needlessly apply the sha256 check with a self-signed cert. Going to sha256 in the NAS avoids the error message from Chrome, but that is all it does.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
