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

*ring* versions prior to 0.17 are unmaintained. #2241

Merged
merged 1 commit into from
Mar 7, 2025

Conversation

briansmith
Copy link
Contributor

No description provided.

@tarcieri
Copy link
Member

tarcieri commented Mar 6, 2025

Perhaps instead of filing a new advisory, you can update RUSTSEC-2025-0007 and remove the withdrawn attribute? That would avoid having two duplicate advisories for the same thing.

@djc
Copy link
Contributor

djc commented Mar 6, 2025

Perhaps instead of filing a new advisory, you can update RUSTSEC-2025-0007 and remove the withdrawn attribute? That would avoid having two duplicate advisories for the same thing.

Not sure that would make sense? The intent seems very different to me.

@briansmith
Copy link
Contributor Author

I guess I agree with djc. If somebody already chose to ignore the earlier advisory then they wouldn't see anything with the update, right?

@tarcieri tarcieri merged commit 849d1a7 into rustsec:main Mar 7, 2025
1 check 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.

3 participants