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

Setting TLS 1.3 as minumum TLS version yields a penalty for not supporting TLS 1.2 #930

Open
rmjansen opened this issue Jun 26, 2023 · 3 comments

Comments

@rmjansen
Copy link

Scanning a site with TLS 1.3 as the minimum required version results in an A. Lowering the minimum required TLS version to 1.2 (with no other changes applied) results in an A+ for the same site. This suggests that the penalty for using outdated TLS versions and not supporting TLS 1.2 is also applied to sites that use TLS 1.3 but not support TLS 1.2.

@ArchangeGabriel
Copy link

Duplicate: #910, #863, #853, #815, #786, #711.
TL;DR: since FALLBACK can’t be tested, you can’t get A+. That’s silly, but the devs never acknowledged this.

@lilyanatia
Copy link

since FALLBACK can’t be tested, you can’t get A+. That’s silly, but the devs never acknowledged this.

it's especially silly since:

  1. downgrades aren't possible if the server only supports one TLS version.
  2. TLS 1.3 includes it's own downgrade prevention mechanism.

@mulder999
Copy link

It's surprising that this issue still hasn't been resolved in 2024. All major browsers have supported TLS 1.3 since 2020 or earlier.

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

4 participants