You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though permission.site gives you the option to connect using HTTP instead of HTTPS, I still feel that it is important for HTTPS to be implemented securely. Please drop support for weak cipher suites for TLS 1.2. See the link below for more details: https://www.ssllabs.com/ssltest/analyze.html?d=permission.site
The text was updated successfully, but these errors were encountered:
permission.site is intended to be used across a wide variety of browsers.
Given that serious security concerns like downgrade attacks are well mitigated in browsers, I'd argue that compatibility with more cipher suites is more useful than the alternative.
In any case, this project uses GitHub Pages for hosting, and that does not allow this level of configuration.
(Alternative hosting would raise barriers to maintenance and contribution.)
Even though permission.site gives you the option to connect using HTTP instead of HTTPS, I still feel that it is important for HTTPS to be implemented securely. Please drop support for weak cipher suites for TLS 1.2. See the link below for more details:
https://www.ssllabs.com/ssltest/analyze.html?d=permission.site
The text was updated successfully, but these errors were encountered: