by kevin » Sun Jan 10, 2016 1:11 pm
Just FYI, the certs that are "stock" are generated at "first boot" for each instance of our image being used. No certs are the same using our image.
That said, please make sure that your ser2sock config file in /etc/ser2sock/ser2sock.conf is also defaulted after removing certificates.
I believe ser2sock will also generate its own certificates in "setup" when you choose to enable the "ssl" option for it - but I could be mistaken there - however with "ssl" option enabled for ser2sock it should be as easy as replacing filenames to certs in the config file and restarting ser2sock and gunicorn.
SSL for ser2sock is different from SSL for HTTPS. Unless you plan on exposing the ser2sock stream outside your network, this can be left alone.
I understand the want for encrypting the ser2sock stream that's why we offer the option, but there are reasons to keep it unencrypted and firewalled as well - currently there is only 1 method outside of the webapp able to connect to and read the encrypted ser2sock stream - the alarmdecoder keypad application. If you want to integrate this into a home automation system - keeping that stream plaintext can be beneficial. Also good for debugging.
Not an employee of the company. Just here to help and keep things clean.