Conversation
7a76522 to
56e7157
Compare
4f37dc0 to
90eee67
Compare
64db9ee to
f944131
Compare
f129cae to
47db372
Compare
this is a crude way to use the new features in python-ecdsa, will need to be reworked later (to use ECDH object)
This file contains hidden or 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.
Use the faster low-level implementation of ECC for ECDHE calculations
We should use the python-ecdsa for parsing now, as it does support X9.62 format, including the compressed point representation, so this is a draft until this happens
see also: #373 and #103
Blocked on tlsfuzzer/python-ecdsa#214 (unblocked now, but we will need new python-ecdsa release to use it)
This change is