NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Mountain Lion Compatibility
Is there any early word on Mountain Lion compatibility for the ReadyNAS models?
sircoolio - this is not necessarily a Server change that needs to be implemented, but a client change.
The ReadyNAS issues a self-signed certificate to enable SSL support (i.e. the "S" in "HTTPS", and self-signed as those do not cost you anything)
Web browsers always warn you before accessing services over HTTPS where the certificate is self-signed and allow you to set the certificate as trusted to avoid future warnings. Finder doesn't have such a feature and has previously always defaulted to trusting the certificate. It appears that security hole has been closed in ML by now defaulting to not trusting self-signed certificates. But as there is no mechanism to ask to trust the certificate built into Finder you must therefore you must use the KeyChain app on your client to first trust the certificate - once done Finder should connect as before
The alternative is to make a server change and buy & install a certificate from a trusted authority (eg Comodo, verisign etc) - you can read how here: http://url.sphardy.com/Romarm
I've just tested connecting to my NAS with trusted certificate installed over HTTPS from Finder on my ML MacBook - works just fine as shown below:
The ReadyNAS issues a self-signed certificate to enable SSL support (i.e. the "S" in "HTTPS", and self-signed as those do not cost you anything)
Web browsers always warn you before accessing services over HTTPS where the certificate is self-signed and allow you to set the certificate as trusted to avoid future warnings. Finder doesn't have such a feature and has previously always defaulted to trusting the certificate. It appears that security hole has been closed in ML by now defaulting to not trusting self-signed certificates. But as there is no mechanism to ask to trust the certificate built into Finder you must therefore you must use the KeyChain app on your client to first trust the certificate - once done Finder should connect as before
The alternative is to make a server change and buy & install a certificate from a trusted authority (eg Comodo, verisign etc) - you can read how here: http://url.sphardy.com/Romarm
I've just tested connecting to my NAS with trusted certificate installed over HTTPS from Finder on my ML MacBook - works just fine as shown below:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
