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 deprecation warning #467

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add deprecation warning #467

wants to merge 1 commit into from

Conversation

DavidBM
Copy link

@DavidBM DavidBM commented Oct 21, 2020

Hi!

So this crate in wonderful and helped a lot some time ago.

Said that, newest commit in this project dates from 5 years ago. Sometimes, when searching things like "scrypt rust" in search engines you get this repository as first result, which is dangerous as it wasn't maintained for 5 year now. See also: https://rustsec.org/advisories/RUSTSEC-2016-0005.html

I think at least this project can show a deprecation warning in the Readme in order to point to https://github.com/RustCrypto/ which is properly maintained.

Hope this PR comes well.
And thanks for all the Job done on this crate.

@dobromyslov
Copy link

@DavidBM thanks for this notice. It helped me to distinguish pros and cons in this question: https://stackoverflow.com/questions/70701405/what-sha256-rust-implementation-take-for-no-std-embedded-device

@tarcieri
Copy link

tarcieri commented Apr 29, 2022

The @rustsec project has filed RUSTSEC-2016-0005 as an advisory that rust-crypto is unmaintained.

The advisory suggests several alternatives.

brainstorm added a commit to umccr/crypt4gh-rust that referenced this pull request Jun 19, 2023
…ute rust-crypto: https://rustsec.org/advisories/RUSTSEC-2016-0005.html

Also coming from unmerged PR DaGenix/rust-crypto#467

This crate change is required to be Crypt4GH spec-compliant (see section 5.1).
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.

3 participants