Updates for Release Candidate 2 #584
Merged
Conversation
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
This commit makes a few cargo-audit-related changes: * updates the lock file with newer, un-yanked versions of futures-... crates * Updates the cargo audit config file to ignore the `chrono` and `time` issues. * Updates the security policy to lay out our approach to handling vulnerability reports. Signed-off-by: Ionut Mihalcea <[email protected]>
ionut-arm
added
enhancement
anta5010
approved these changes
Feb 21, 2022
anta5010
approved these changes
Feb 24, 2022
ionut-arm
force-pushed
the
audit-update
branch
from
28f698f to
98474c6
Compare
Since the `rust-cryptoauthlib` crate isn't currently maintained, and given that it seems to have some issues with cross-compilation for armv7, we're removing the CAL provider from `all-providers` until we can get it properly built and maintained. Signed-off-by: Ionut Mihalcea <[email protected]>
ionut-arm
force-pushed
the
audit-update
branch
from
98474c6 to
69642f6
Compare
Fixing some of the clippy lints introduced in 1.59.0 Signed-off-by: Ionut Mihalcea <[email protected]>
anta5010
reviewed
Feb 28, 2022
ionut-arm
force-pushed
the
audit-update
branch
from
6ccd2cc to
e42824c
Compare
anta5010
approved these changes
Feb 28, 2022
The TS provider is currently excluded from the cross-compilation tests. However, `libts` can be cross-compiled for aarch64-linux-gnu targets. The `trusted-service-provider` feature is added here to cross-compilation for the appropriate target only. Signed-off-by: Ionut Mihalcea <[email protected]>
paulhowardarm
approved these changes
Mar 1, 2022
There was a problem hiding this comment.
I am assuming that the CAL provider can still be explicitly built as a feature and used as normal, despite the removal from all-providers? That's what it looks like to me, but I want to double check because I don't think we should be deactivating the provider completely in such a significant milestone release.
We should aim to get this back into all-providers ASAP, but I see we have an issue to track that, so that's good.
Yes, I guess one could say that |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit makes a few cargo-audit-related changes:
futures-... crates
chronoandtimeissues.handling vulnerability reports.
cryptoauthlib-providerfromall-providersaarch64-linux-gnu)