73
Figure 85:
Settings Confirmation
6.1.2
RCCMD with own SSL certificates
In this chapter we will describe, how to use an own SSL certificate with RCCMD, e. g.
OpenSSL (
Be your own CA
Using OpenSSL it is quite simple to become your own CA. Just run:
CA.pl –newca
Done! Just ensure, that you select a useful CN (common name)!
Create your RCCMD certificate
You need to create your certificate for RCCMD now. As it will use it for verification, it should
contain the same useful common name (CN), that you selected for the CA. The private key
must not be encrypted to let the RCCMD Client (service) start without trouble. Therefore we
use the “–nodes” option and the “-newreq” command:
CA.pl –newreq -nodes
Sign with your CA:
CA.pl –sign
Now create an empty file
named “rccmd.pem“ and copy the cert information of
newcert.pem
(rccmd certificate),
newkey.pem
(private key) and
cacert.pem
(CA) into it. Please note, that the
exact copying is required to use it without trouble!
Use your own RCCMD certificate
Do the following steps at the RCCMD Client and every sender (e. g. UPS Web Manager):
Backup the existing “rccmd.pem”
Replace the existing “rccmd.pem” with your own
Restart the RCCMD Client
Restart the RCCMD Sender
6.1.3
RCCMD client as relay station
In order to reach a bigger number of RCCMD receivers, the adapter needs to be operated as
relay station. The receiver will be configured so that it will receive a RCCMD signal and this
signal is then used to start a batch file, which then starts even more RCCMD sender signals.
