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

Client test incorrectly reports "No" instead of "Firewall" when port 10303 is blocked #607

Closed
robmoss2k opened this issue May 4, 2018 · 1 comment

Comments

@robmoss2k
Copy link

commented May 4, 2018

If you perform the test on a client that isn't able to communicate on non-standard ports, you get TLS 1.3 support as "No" and TLS 1.2 and earlier support as "Firewall", as detailed in the following thread:

https://community.qualys.com/thread/18279-ssllabs-tls-capabilities-output-different-from-chrome

I believe the following two lines should be inserted at line 271, although I'm not able to test:

jQuery('#protocol_tls1_3').text('Firewall');
jQuery('#protocol_tls1_3').css('color', 'red');

@tamthing

This comment has been minimized.

Copy link

commented Jan 25, 2019

This has now been fixed on version 1.32.15.

@tamthing tamthing closed this Jan 25, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.