Support Elliptic Curve Private Keys #428
Merged
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
hannesdejager
force-pushed
the
hannes/sec
branch
3 times, most recently
from
a77158b
to
254aa1d
Compare
We didn't support elliptic curve private keys. See bolcom/unFTP#126 . I took the opportunity to also improve the error handling in the TLS code.
hannesdejager
force-pushed
the
hannes/sec
branch
from
254aa1d
to
3a999ef
Compare
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.
Fixes this unFTP issue: bolcom/unFTP#126
I also improve the error handling to provide more user friendly error messages.