Support performing OpenSSL::Digest::MD4 in openSSL 3 by loading legacy provider #63
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
…y provider openSSL3 doesn't support MD4 which means any installation with ntlm on openSSL3 using the challenge will be breaking. Hence the loading of the provider. I wonder if its possible to move away from MD4 altogether?
This was referenced Jun 5, 2024
|
thanks, unfortunately it appears md4 is part of the ntlm spec so it cannot be removed. I will be closing this in favor of #53 since that PR seems more future-proof |
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.
openSSL3 doesn't support MD4 which means any installation with ntlm on openSSL3 using the challenge will be breaking. Hence the loading of the provider. I wonder if its possible to move away from MD4 altogether?
related: #57