git-config: secure access to paths and other values #460
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.
That way we are able to load untrusted repositories and simply skip configuration that
isn't trusted by the current user, typically the repository-local one.
As each file has a trust-level associated with it, we can use that possibly as well.
Tasks
git-sec
, it should probably know about theTrust
associated with a config file. This is forgit-repository
which should make it mandatory to access paths that way.