This article provides the steps required in order to provide your own certifications to your SoftNAS instance.
An SSL certificate is necessary for more than just distributing the public key. If it is signed by a trusted third-party, it verifies the identity of the server so clients know they aren’t sending their information (encrypted or not) to the wrong person.
What is a Self-Signed Certificate?
It is a certificate that is signed by itself rather than a trusted third party. This is not a good idea for most business use cases. You will almost never want to use a self-signed certificate on a public Apache server that requires anonymous visitors to connect to your site because they could easily become a victim of a man-in-the-middle attack.
When could a Self-Signed Certificate prove adequate?
Apache development server - There is no need to spend extra money buying a trusted certificate when you are just developing or testing an application.
Intranet - When clients only have to go through a local Intranet to get to the server, there is virtually no chance of a man-in-the-middle attack.
Personal sites with few visitors - If you have a small personal site that transfers non-critical information, there is very little incentive for someone to attack the connection.
In other words, when deploying your SoftNAS server into an enterprise use case, it may be required (or at least strongly recommended) that you switch the default self-signed certifications for your own enterprise certifications.
If you want to send or receive messages signed by root authorities and these authorities are not installed on the server, you must add a trusted root certificate manually.
Append your trusted certificate, and set the desired path using the following commands: