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
Can the salsa20 family be pushed to crates.io? #15
Comments
I think it's ok to publish as is, although I think it'd be nice to find some way to factor it into |
I would be willing to give that refactoring a stab if given some guidance on what is desired. Salsa20 and ChaCha20 share |
That's one possible approach, yes |
I've registered @tarcieri |
@newpavlov excellent, thanks |
Wow, that's a quick response. Would you like me to submit a PR or do this refactoring yourselves? |
I think it will be faster for you to create a PR. Also we always welcome new contributors. :) |
Great, I'll get right to it! |
Would you like to keep the |
Probably not. It's just a name we picked in the course of the PR. |
I don't think we need a meta-crate, in my experience they are rarely used in practice. So lets use only 3 crates. BTW while you at it, please update table in README with the added crates. |
OK, I think the PR #16 is ready for review now. |
Now that #16 is merged, I have published (and pushed tags for) the following releases: Thanks @emc2 for the implementation work and @sseemayer for the refactoring work! |
Similar to #2, I am migrating away from
rust-crypto
and would like to use the Salsa20 and ChaCha20 implementations contained instream-ciphers
. Would it be possible to push them to crates.io?The text was updated successfully, but these errors were encountered: