-
Notifications
You must be signed in to change notification settings - Fork 269
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
RIPEMD-320 implementation #68
Conversation
The travis-ci fail on Rust 1.21.0 seems unrelated to my changes.
|
Thank you for your PR! At first glance it looks good to me, I will check it a bit more thoroughly on the next week and will probably merge it immediately after that. I've yanked block-buffer v0.7.1, it's great that we found it thanks to your PR and not by breaking someone's build. But there is still a small problem in your code which should be fixable with a simple |
Hey @newpavlov . Thanks for your comment! Do you mean you want me to change the call to |
Yes, exactly this. I think it will be better for you to do it. |
f72702b
to
98bd689
Compare
98bd689
to
72eebda
Compare
I have updated the PR. |
Hey @newpavlov, happy new year! Any news on this? :-) |
@newpavlov or anyone, could we get this merged? 🙏 🙂 |
Try again? |
@tarcieri the build now fails on Rust 1.21.0 for the same reason as the first time -- that is, |
@magnet unfortunate... any ideas @newpavlov ? |
Arrrgh, I've added And sorry for the long waiting time! I couldn't find time to properly review PRs. I will do my best to do it either on this or next weekend. |
Thanks @newpavlov ! The checks are green finally 🙂. |
Thank you again! It will be nice if you'll share publishing rights to |
@newpavlov Thanks for merging, I had already sent you an invite, and just sent a new one to you and |
This partly addresses issue #13.
This RIPEMD-320 implementation is based on the existing RIPEMD-160 implementation. It would be possible and relatively easy to refactor code to avoid so much duplication, but making this a separate crate breaks less code and makes it easy to add.
RIPEMD-160 and RIPEMD-320 also share a similar relationship as RIPEMD-128 and RIPEMD-256 do. A quick diff between RIPEMD-160 and RIPEMD-320 implementations should be useful anyone writing RIPEMD-128/256.
I don't know if that's OK with regard to the conventions in place, but in the tests I drew some samples from the RIPEMD-160 webpage[1] that describes expected hashes for some strings.
Also, I have uploaded a
0.8.0-rc1
version tocrates.io
(under the nameripemd320
). If/when you can merge this into master and publish, please ping me so I can give you access and optionally yank the rc1.[1] https://homes.esat.kuleuven.be/~bosselae/ripemd160.html