-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add Cargo features and code to allow OpenSSL to be used for Crypto #40
Conversation
@moznion can I please get a feedback on this? |
@moznion can I please get feedback on this? |
@ramaravishankar Thank you for your contribution. Please give me a time to take a look at this. |
@moznion sorry for bugging again, we have a dependency on this change, would it be possible for you to review this week? |
@ramaravishankar I really appreciate your contribution! It seems some of Windows tests failed but the core of the change seems good. I'll merge this pull request and publish the new version which includes this change. Once it has been finished, I'll let you know that. |
@ramaravishankar I published v0.4.0 which includes this change. Thank you for your contribution! |
Thanks @moznion, cheers 🎉 |
Hi - thanks for sharing this library!
This change is to add support for using OpenSSL for cryptography instead of the MD5 crate - for cases where only a trusted OpenSSL implementation is supported for anything cryptography related. There's no functional change to the output of the library.
I've added this as a cargo feature so that the MD5 crate is still used by default so as not to impact existing users who don't want the OpenSSL dependency. Using one feature doesn't compile in the dependencies of the other.
I've also added extra workflow steps to test the two feature options explicitly and confirmed these pass.
Let me know if you have any comments.
If you do accept, would you be able to tag a new release as well please?
Thanks again!