FAQ(s)

⌘K
  1. Home
  2. FAQ(s)
  3. Network & Modem
  4. TLS Ciphers & Certificates

TLS Ciphers & Certificates

Q: “Access denied” to a secure server (HTTPS, FTPS, MQTTS or SMTPS).

A: Secure access depends on server side installed server certificate, TLS version and chosen ciphers .

T: You can verify the server’s TLS/SSL configuration and certificate chain using various online tools, for example: https://www.immuniweb.com/ssl

Enter the <fqdn> : <server port> combination

 A list with supported TLS versions and available cyphers is generated and can be used to select an valid option to build a secure connection.

In the “Certificate Chain” result page. Certificates can be downloaded in .PEM format. (Using the “download” buttons).

ML-x17 series data loggers

TLS-version

Data loggers equipped with ME910, ME310 or LE310 modems, support TLS 1.2 with automatic fallback to TLS 1.1.

In addition, the ME910 and ME310 modems support TLS 1.3. Consequently, the server must support TLS 1.1 or later.

Ciphers

The data logger proposes a list of commonly used TLS cipher suites for the server to choose from. Only if the server is configured to use a cipher suite that is not included in this list does the data logger need to be configured to use that specific cipher suite via the AT#SSLSECCFG modem AT-command.

Certificates

When server certificate verification is enabled and If the server uses a self-signed certificate or a certificate that is not signed by one of the trusted CA certificates preloaded in the data logger, the data logger cannot verify that the server is legitimate, causing the TLS connection to fail.

The ME910 (WW type) modem on a ML-417xxx Data Logger supports TLS version 1.3. (With fallback to a lower version).  Only the cypher sets should be checked.

Other modems types are supporting maximum TLS version 1.2.

The (ftp or web) server must support a minimum TLS version 1.2.

Disable TLS V1.3

To check and change the TLS version, use the COM option from maintenance menu to connect to the modem and execute the AT#SSLSECCFG2 command.

If TLS V1.3 key exchange is not supported, usage can be switched to TLS V1.2 by applying this command:

AT#SSLSECCFG2=1,3,1,1,1,1

Note: The “3” in this command is confusing as it means use TLS V1.2…

Check on (modem) TLS version and loading certificates into the modem is explained in this FAQ.

ML-525xx series data loggers

From YdocTerminal version 3.30, CA certificate files can be browsed and loaded using the Windows file manager.

Note: The ML-525PE menu modem is supporting only one certificate and has TLS V1.2 implemented.

Note: On the ML-525LE, default, three certificates are loaded, covering 99% of available Server certificates.

Loading certificate(s).

CA certificates

[0] Exit

[1] Certificate 1     >> Lets encrypt

[2] Certificate 2     >> Not used (Example automated procedure)

[3] Certificate 3     >> Not used

[4] Certificate usage >> Disabled

[5] Upload to Modem   >> Done

> 2

>Certificate name: GlobalSign Root

Paste CA certificate content below, then press <Ctrl>Z

>—–BEGIN CERTIFICATE—–

MIICCzCCAZGgAwIBAgISEdK7ujNu1LzmJGjFDYQdmOhDMAoGCCqGSM49BAMDMEYx

.

.

+RHUjE7AwWHCFUyqqx0LMV87HOIAl0Qx5v5zli/altP+CAezNIm8BZ/3Hobui3A=

—–END CERTIFICATE—–

Press any key! >

To complete, upload the certificate to the modem.

Certificate usage is configurable. (Enable or disable).

If the server uses a self-signed certificate, the data logger can’t verify if it is valid. (With the standard CA-certificates installed).

Due European RED regulations, certificate verification is default.

To use the certificate (without verification), disable certificate verification in the data logger modem.

CA Certificates

[0] Exit

[1] Certificate 1     >> Test CA

[2] Certificate 2     >>

[3] Certificate 3     >>

[4] Certificate usage >> Enabled

[5] Upload to Modem   >> Not done

>Certificate usage (0 = Disabled, 1 = Enabled): 0

ATE0;&K3;#FTPCFG=100,1,0;#SSLEN=1,1;#SSLCFG=1,1,0,40,10,1;#SSLSECCFG2=1,4,1,0,0

OK

AT#SSLSECCFG?

#SSLSECCFG: 1,0,1

OK

AT#SSLSECCFG=1,0,0

OK

Press any key! >

Tooling on Windows

On a Windows environment, openssl.exe can be installed for a command line version tool.

C:> openssl.exe s_client -connect <broker address>:<port>

How can we help?