TLSv1.2 - Client - test Skipped

[travellingmonk]

Device under testing communicates with an external server over port 80, and this test seems to have been skipped by Testrun. Please see screenshot attached

[jhughesoti]

Network capture indicates outbound connections on port 80 via non TLS connections. The TLS tests are specifically around confirming any outbound TLS connections are valid. This doesn't appear to be indicative of a invalid TLS test but rather a new requirement to monitor all outbound traffic on specified ports for unencrypted services.

[ptorrent]

Hello same issue there

security.tls.v1_2_server | TLS 1.2 validated: Certificate has a valid time range RSA key length passed: 2048 >= 2048 Authorized Certificate Authority signature confirmed. TLS 1.3 validated: Certificate has a valid time range RSA key length passed: 2048 >= 2048 Authorized Certificate Authority signature confirmed. | Compliant

security.tls.v1_2_client | No client hello packets detected | skipped

We're not listening on port 80

[ptorrent]

How can we solve this issue ? Do I've to update testrun ?

[travellingmonk]

@ptorrent hi, if I'm not wrong this issue was solved in the latest firmware release https://www.weble.ch/iot/releases/

[ptorrent]

really ? Yesterday the test was passing, this morning not. Seems a bit random. What is a TLS1.2 hello packet ?

I'm already on last weble version

[travellingmonk]

@ptorrent sorry I misunderstood your message. I thought you were talking about the packet capture screenshot right on the top, where you can see communication over Port 80.
Issue about TLS client, it is currently being address as it is a bug. Please see #242
this will be corrected in an upcoming patch release

[ptorrent]

Unitil this new release, now way to make it compliant ?

If I force TLS 1.3, will it help ?

[ptorrent]

Maybe I found a solution for it on our webserver... Is there a way to test only TLS ?

[jboddey]

Hi @ptorrent. In the device configuration, you can disable the other test modules if required.

[jboddey]

This has been resolved in v1.1.2