Allow non-HTTPS Git URLs for the advisory database#426
Merged
mergify[bot] merged 1 commit intoEmbarkStudios:mainfrom May 19, 2022
Merged
Allow non-HTTPS Git URLs for the advisory database#426mergify[bot] merged 1 commit intoEmbarkStudios:mainfrom
mergify[bot] merged 1 commit intoEmbarkStudios:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #412
The check was apparently added because
rustsecdoesn't support non-HTTPS URLs, butcargo-denydoesn't actually userustsecto fetch the repo;cargo-denyfetches it itself with thegit2crate or thegitexecutable and then passes the repo torustsecas a local filesystem path. And indeed, after removing the check I'm able to use anssh://URL for the advisory database without any problem. So, as far as I can see, the check is unnecessarily restrictive.