tests: Create separate self-signed EC key for tlsfuzzer testing #490
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.
Description
Follow up from #488, where we found the tlsfuzzer has problems with heterogeneous CA + server keys. This creates separate EC key outside of the main CA chain (EC Peer key used for ECDH generally), which turned out to be easier than I expected. It also simplifies the setup a bit and removes the excluded test cases, that should be working.
Checklist
Reviewer's checklist: