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

Tracking issue: Update "default" and "default_fips" to support TLS1.3 #4765

Open
3 of 12 tasks
toidiu opened this issue Sep 11, 2024 · 0 comments
Open
3 of 12 tasks

Tracking issue: Update "default" and "default_fips" to support TLS1.3 #4765

toidiu opened this issue Sep 11, 2024 · 0 comments

Comments

@toidiu
Copy link
Contributor

toidiu commented Sep 11, 2024

Security issue notifications

As a modern TLS library, s2n-tls aims to provide sane and safe default. The goal of this task is to add TLS1.3 support to the "default" and "default_fips" policies.

Project plan:

Post MVP:

  • script to clean up double instances of s2n_config_set_cipher_preferences after auto gen script
 s2n_config_set_cipher_preferences(client_config, s2n_auto_gen_old_default_security_policy());
 s2n_config_set_cipher_preferences(client_config, "20170210");

Extra:

Pin to number policy (failed solution):

This solution was trying to pin current tests to the numbered equivalent of the default policy. However, this could cause a regression of "default" policy tests (tests which actually wanted to test the "default" policy). Since there is no easy way to detect these type of tests, we cannot pin tests to a numbered policy without risking regression.

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

No branches or pull requests

2 participants