What will the data logger do if it has TLS enabled and connects to a server who offers a certificate that is not verified by a "trusted" signer?
Are there any "trusted" signers as far as the logger is concerned?
I am seeing a delay in the communications and then progress continues - this delay may or may not just be part of the certificate reading and encrypting process, but I'm wondering about whether there will be any difference if the certificate is signed or not?
Thanks
Simon
Simon,
The datalogger does not differentiate between a self-signed and a signed certificate.
The delay in communications is because the datalogger is working its way through the certificate and setting up the encryption in order to continue with secured communication. It is dependent on the processing power of the datalogger. The CR3000 does it faster than a CR1000 but there is still some delay.
-Gary