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

Add support for RIPEMD160 digest #55

Merged
merged 4 commits into from
Dec 13, 2024
Merged

Conversation

huskcasaca
Copy link
Contributor

RIPEMD160 is widely used and supported by BouncyCastle and OpenSSL3. However, RIPEMD128, RIPEMD256, and RIPEMD320 are not supported by OpenSSL3. I'm not sure if it’s necessary to add the others.

Copy link
Owner

@whyoleg whyoleg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

Let's start with just supporting RIPEMD160, as it's supported in at least 2 providers.
This is some kind of "rule" at my side, as I don't see a reason currently to support algorithms, which are available only on one platform (may change in future).
Plus, as far as I understand, only RIPEMD160 is widely used

@whyoleg whyoleg added this to the 0.4.1 milestone Dec 5, 2024
@huskcasaca huskcasaca changed the title Add support for RIPEMD digest Add support for RIPEMD160 digest Dec 11, 2024
@huskcasaca huskcasaca requested a review from whyoleg December 12, 2024 08:35
Copy link
Owner

@whyoleg whyoleg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!
Let's try not to change CI configuration

include:
- os: 'macos-latest'
target: 'macos'
- os: 'windows-latest'
target: 'native'
- os: 'ubuntu-24.04'
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there some problem with ubuntu-latest?
There were no problems before, so I don't think that it's needed for this PR
Could you please revert those changes and I will re-run CI?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried not to change but ubuntu-latest is 22.04 which is using OpenSSL 3.0.2. It dropped RIPEMD160 to legacy providers which requires an extra config file to reenable it otherwise the CI will fail.
But OpenSSL 3.0.6 reverts the drop so I have to update to ubuntu-24.04 with OpenSSL 3.0.8+.

openssl/openssl#16994
https://openssl-library.org/news/openssl-3.0-notes/

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I see, thanks for the explanation!

include:
- os: 'macos-latest'
target: 'macos'
- os: 'windows-latest'
target: 'native'
- os: 'ubuntu-24.04'
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I see, thanks for the explanation!

@whyoleg whyoleg merged commit 186a420 into whyoleg:main Dec 13, 2024
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants