Conversation
Version 0.1 of the `time` crate has a vulnerability. Apparently it does not affect the `chrono` crate, which is the crate that depends on `time`, but it's better to be safe. We don't actually need the default `chrono` feature of `fatfs`, so we can easily remove both `chrono` and `time` from our dependency tree by disabling that feature.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 0.1 of the
timecrate has a vulnerability. Apparently it does not affect thechronocrate, which is the crate that depends ontime, but it's better to be safe. We don't actually need the defaultchronofeature offatfs, so we can easily remove bothchronoandtimefrom our dependency tree by disabling that feature.