(Created page with "SSL certificates can be used to set up client authentication and encryption of your alarm data. Currently the only supported method of serving the AlarmDecoder over SSL is th...") |
|||
| Line 1: | Line 1: | ||
| + | {{PageHeading| | ||
SSL certificates can be used to set up client authentication and encryption of your alarm data. Currently the only supported method of serving the AlarmDecoder over SSL is through [http://github.com/nutechsoftware/ser2sock ser2sock], though support is destined for [[AlarmDecoderGUI]] in the future. | SSL certificates can be used to set up client authentication and encryption of your alarm data. Currently the only supported method of serving the AlarmDecoder over SSL is through [http://github.com/nutechsoftware/ser2sock ser2sock], though support is destined for [[AlarmDecoderGUI]] in the future. | ||
As for the client side, it is currently supported in the [[AlarmDecoderGUI]] and the [http://github.com/nutechsoftware/alarmdecoder python library]. | As for the client side, it is currently supported in the [[AlarmDecoderGUI]] and the [http://github.com/nutechsoftware/alarmdecoder python library]. | ||
| + | }} | ||
| − | =Generating Certificates= | + | |
| − | ==Generating a certificate for the Certificate Authority== | + | ==Generating Certificates== |
| + | ===Generating a certificate for the Certificate Authority=== | ||
We use an intermediate certificate known as a Certificate Authority in order to provide an authentication mechanism for the AlarmDecoder devices. This allows you to restrict access to the service to only those certificates that have been signed by the CA. This also allows you to revoke client certificates or even regenerate the CA certificate itself should it get compromised. | We use an intermediate certificate known as a Certificate Authority in order to provide an authentication mechanism for the AlarmDecoder devices. This allows you to restrict access to the service to only those certificates that have been signed by the CA. This also allows you to revoke client certificates or even regenerate the CA certificate itself should it get compromised. | ||
TODO | TODO | ||
Latest revision as of 23:29, 21 December 2013
SSL certificates can be used to set up client authentication and encryption of your alarm data. Currently the only supported method of serving the AlarmDecoder over SSL is through ser2sock, though support is destined for AlarmDecoderGUI in the future.
As for the client side, it is currently supported in the AlarmDecoderGUI and the python library.
Generating Certificates
Generating a certificate for the Certificate Authority
We use an intermediate certificate known as a Certificate Authority in order to provide an authentication mechanism for the AlarmDecoder devices. This allows you to restrict access to the service to only those certificates that have been signed by the CA. This also allows you to revoke client certificates or even regenerate the CA certificate itself should it get compromised.
TODO