Switch mozilla-modern to wildcard-ecc256 #539
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility asks for ECDSA only, so switching from
wildcard-normal.conftowildcard-ecc256.confseems to match it better.I'm not making any additional #483 changes for now, to not interfere with @christhompson's work on 6f64093 (that looks great! and addresses many other updates), so this is just to complement the nginx/VM updates underway that also include major bumps of the mozilla-* configs.