-
Notifications
You must be signed in to change notification settings - Fork 372
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 disclosure for hasbrown's borsh encoding #2100
Conversation
There was a proposal to release the fix as 0.15.1 and just yank 0.15.0, so, might be worth verifying which of the two versions is going to be used for the fix. |
It's unclear with what version it will be and when it will be. I'd prefer to make this valid and file-able now than risk someone starting to use this functionality (which will make removing it more complicated).
I've removed the patched notice so this can be filed now (warning other people off from adopting this functionality) while we continue to wait for a patched version. |
Sorry for my delay in updating this. It correctly notes when patched now. |
|
||
[versions] | ||
patched = [">= 0.15.1"] | ||
unaffected = ["<= 0.14"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure how this is supposed to be interpreted, but at least cargo-deny flags 0.14.5
as being affected now. Maybe unaffected = ["< 0.15.0"]
would be better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've opened #2157 with that proposal
I wrote this as fixed in 0.16 due to that being the plan documented here: rust-lang/hashbrown#570 (comment)
Until that PR is merged and 0.16 is released, this cannot be merged/must be edited to be described as unpatched.