You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't plan on doing a competing implementation without a good reason (e.g. substantial improvements/fixes which @Keats will not accept to his crate for some reason or support of hypothetical password hashing trait). Though I still would be happy to accept the crate transfer if he''ll change his mind.
I can give a shot for Argon2, since there is already a Rust implementation and that RustCrypto already has Blake2. Are you still looking for someone to implement it here?
Since argon2rs has not been updated for the last 2 years and the maintainer is not answering on the ticket, what about asking the maintainer of https://github.com/sru-systems/rust-argon2 instead? It works on WASM even with multiple lanes, supports multithreading via features, supports Argon2id and is still maintained. Biggest weak point for now is the lack of SIMD.
For the record, one cons of all existing Argon2 implementations is a lack of no_std mode which is de-facto for RustCrypto crates. It means there is no easy way to "import" any of these crates into RustCrypto family seamlessly.
We now have an argon2 crate based on the reference implementation, however it might be worth looking at reusing some code from argonautica (which is MIT/Apache2) for SIMD. See #104.
For your awareness, I'm working on an Internet-Draft for a modified version of Balloon called BKDF, which would represent a proper specification of Balloon. It's not finalised as I'm still trying to collect feedback on the design/design ideas from cryptographers, but it contains a number of improvements already.
I would greatly appreciate feedback on the draft/design from the Rust Crypto maintainers/contributors, especially @tarcieri since you were a PHC judge. I will acknowledge people in the Acknowledgments section with their permission.
The current yescrypt crate is based on a translation of the reference implementation in C. I'm not familiar with yescrypt, but it seems to be based on scrypt, so maybe yescrypt crate could be rewritten based on the existing scrypt crate.
Activity
dignifiedquire commentedon Nov 19, 2018
I have an implementation of AES KW as defined here:
https://tools.ietf.org/html/rfc339, is that of interest?
astonbitecode commentedon Mar 14, 2019
Does this issue mean that RustCrypto will not include bcrypt password hashing?
Or maybe there will be yet another implementation of it in this repo?
newpavlov commentedon Mar 14, 2019
I don't plan on doing a competing implementation without a good reason (e.g. substantial improvements/fixes which @Keats will not accept to his crate for some reason or support of hypothetical password hashing trait). Though I still would be happy to accept the crate transfer if he''ll change his mind.
zer0x64 commentedon Aug 22, 2019
I can give a shot for Argon2, since there is already a Rust implementation and that RustCrypto already has Blake2. Are you still looking for someone to implement it here?
zer0x64 commentedon Feb 24, 2020
Since argon2rs has not been updated for the last 2 years and the maintainer is not answering on the ticket, what about asking the maintainer of https://github.com/sru-systems/rust-argon2 instead? It works on WASM even with multiple lanes, supports multithreading via features, supports Argon2id and is still maintained. Biggest weak point for now is the lack of SIMD.
fadeevab commentedon Apr 12, 2020
@zer0x64 Thank you for information!
fadeevab commentedon May 12, 2020
For the record, one cons of all existing Argon2 implementations is a lack of
no_stdmode which is de-facto for RustCrypto crates. It means there is no easy way to "import" any of these crates into RustCrypto family seamlessly.tarcieri commentedon Jun 10, 2020
We should definitely ping one of the existing authors to see if they want to collaborate.
Otherwise, we can fork one of the existing crates, add
no_stdsupport, and then release it asargon2.newpavlov commentedon Jun 10, 2020
I've already pinged them in the past, see issues linked in the OP list.
tarcieri commentedon Jun 10, 2020
@newpavlov what about the maintainer of rust-argon2 as @zer0x64 mentioned?
newpavlov commentedon Jun 10, 2020
Done, see the linked issue.
zizhengtai commentedon Jun 17, 2020
There is also argonautica which supports SIMD.
tarcieri commentedon Jan 29, 2021
We now have an
argon2crate based on the reference implementation, however it might be worth looking at reusing some code fromargonautica(which is MIT/Apache2) for SIMD. See #104.daxpedda commentedon Mar 21, 2022
We can mark Balloon (and also fix the typo) as done, see https://crates.io/crates/balloon-hash.
samuel-lucas6 commentedon Sep 3, 2024
For your awareness, I'm working on an Internet-Draft for a modified version of Balloon called BKDF, which would represent a proper specification of Balloon. It's not finalised as I'm still trying to collect feedback on the design/design ideas from cryptographers, but it contains a number of improvements already.
I would greatly appreciate feedback on the draft/design from the Rust Crypto maintainers/contributors, especially @tarcieri since you were a PHC judge. I will acknowledge people in the Acknowledgments section with their permission.
sorairolake commentedon Nov 21, 2024
The current
yescryptcrate is based on a translation of the reference implementation in C. I'm not familiar with yescrypt, but it seems to be based on scrypt, so maybeyescryptcrate could be rewritten based on the existingscryptcrate.