Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS report module empty and security.tls.v1_2_server & security.tls.v1_3_server reports Feature Not Detected even though HTTPS supported #1144

Open
duncangreene opened this issue Feb 19, 2025 · 1 comment

Comments

@duncangreene
Copy link

Describe the bug
This is somewhat similar to #1083, but differs in that security.tls.v1_2_server and security.tls.v1_3_server additionally reported "Feature Not Detected".

Image
Image
Image

We subsequently connected DUT to an ordinary DHCP server and observed the below cert presented after less than a minute of power up.

Image

Error logs
QSC QIO-L4O v9.13.0-2412.002 (test 2).zip

Environment (please provide the following information about your setup):

  • Version 2.1
@jhughesbiot
Copy link
Collaborator

The handshake is failing during the initial TLS connection. Without more information on the devices TLS configuration however, there is not much I can add to the reason why it is rejecting the connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants