It is safe to overwrite as it can easily be regenerated in frontview if needed. Note that in this last step you will have to overwrite an existing file which is the current certificate and which therefore causes the warnings we are trying to fix. Create a single text file that contains both your Prvate Key Certificate and your Personal Public Certificate appended immediately after it - copy this file to your NAS as /etc/frontview/apache/apache.pem If provided, copy the intermediate certificate to a text file called: /etc/frontview/apache/addons/intermediate.pem Copy the Global Certificate Authority Root Certificate to text file called: /etc/frontview/apache/addons/gs_root.pem This can only be done by remotely logging into your NAS as root via SSH - so log in, and follow these steps: Note that item 2 is optional depending on the issuing authority.
I obtained my Certificate via my Domain Registrar who have a co-operation with Alpha SSL.
#Readynas acrosync setup ssh how to
Providing details of how to obtain a certificate and from where is beyond the scope of this post as the process can vary significantly from provider to provider. The process also assumes that you also have a domain name assigned to your NAS - if you don’t then you cannot obtain an SSL certificate. If you you don’t, or you don’t understand what this means - stop now. Note: This process assumes you have sufficient knowledge to SSH into your NAS as the root user and to work at the linux command line.
#Readynas acrosync setup ssh install
The following is the manual process to install that certificate on your ReadyNAS devices
If you have such a certificate, or buy one, unfortunately Netgear has yet to see fit to provide a mechanism for installing it ( unlike their competition), so getting rid of the confusing warning message for your users and ensuring secure communication to your NAS. In addition to Certificate authorits like Verisign, many ISPs and Domain Registrars offer their customers cheap SSL certificates.
The above warnings occur when you do not have a certificate that has been signed by a 3rd party Certificate Authority. This allows your web browser to verify you are talking to your NAS and not some other server pretending to be your NAS, and then enables encrypted data transfers. More importantly, how often do other users of your NAS see such warnings? And do they know what to do to avoid them, or understand that they are not some kind of fatal error and that your website or NAS access is working just fine?Īn SSL certificate is a means by which web servers prove their identity to web browsers and is digitally “signed” by a certificate authority, such as Verisign, that web browsers already trust. How often have you seen a warning like this?
0 kommentar(er)
