HTTPS, ReadyNAS Duo V2 and Chrome

Well, there is general agreement that sha1 needs to be deprecated for PKI certficates. However, they aren't used in self-signed or root certificates in the same way.

There are four basic ways it could play out:
-Google changes the behavior of Chrome with self-signed certs
-Netgear decides to generate self-signed certs with sha256
-you uninstall the cert, and revert to the warning I am seeing.
-People stop using Chrome with the NAS (using IE or Firefox instead).

If its an outdated certificate....surely it would be in Netgears interest to stop the units being hacked
Does this problem still exist with the new breed of NAS with iOS 6.
Is it a case of going on bended knee and asking Netgear to consider upgrading to sha256

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.