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

Cipher_suites table on wiki may no longer be generated automatically, and therefore stale. #247

Open
charlesmanser opened this issue May 17, 2019 · 4 comments · May be fixed by #296
Open

Comments

@charlesmanser
Copy link

https://wiki.mozilla.org/Security/Server_Side_TLS#Cipher_suites states that the table is automatically generated via https://github.com/marumari/tls-table/blob/master/tls-table.py. That returns a 404, not found error.

The table may be stale now. It seems to recommend TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 as intermediate; however, sections like "Intermediate compatibility (default)" and https://statics.tls.security.mozilla.org/server-side-tls-conf.json do not recommend CBC-based ciphers.

@floatingatoll
Copy link

floatingatoll commented May 17, 2019 via email

@april
Copy link
Contributor

april commented May 24, 2019

It was always generated manually, and it uses the cipher suites on the wiki page, not the JSON (which I'm not sure existed at the time). It has been updated, but I'm keeping this open until everything is synced.

https://wiki.mozilla.org/Security/Cipher_Suites

@charlesmanser
Copy link
Author

For example, when I check out https://wiki.mozilla.org/Security/Cipher_Suites, I see green highlighted TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384; however, https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility does not list any CBC/-cbc- ciphers.

@janbrasna
Copy link

janbrasna commented Dec 22, 2023

Should be updated now with v5.7 — although manually as seen in #296

Issues with generating by tls-table tracked:

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

Successfully merging a pull request may close this issue.

4 participants