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

support for setting hashfunc on verifying key load #167

Merged
merged 1 commit into from Dec 16, 2019

Conversation

tomato42
Copy link
Member

All the other methods for creating the keys (both Signing and Verifying)
allow setting the default_hashfunc, add the parameter to the last
two of them

also a bit of whitespace cleanup

fixes #72

@tomato42 tomato42 added the feature functionality to be implemented label Nov 30, 2019
@tomato42 tomato42 added this to the v0.15 milestone Nov 30, 2019
@tomato42 tomato42 self-assigned this Nov 30, 2019
@coveralls
Copy link

coveralls commented Nov 30, 2019

Coverage Status

Coverage increased (+0.05%) to 96.345% when pulling d5e75ca on tomato42:hash_for_pem into 8deb089 on warner:master.

All the other methods for creating the keys (both Signing and Verifying)
allow setting the default_hashfunc, add the parameter to the last
two of them

also a bit of whitespace cleanup
@tomato42 tomato42 merged commit 7cf99f0 into tlsfuzzer:master Dec 16, 2019
@tomato42 tomato42 deleted the hash_for_pem branch December 16, 2019 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature functionality to be implemented
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Loading veryfying key from pem or der always defaults to sha1 hash function
3 participants