Fix leak tag create from buffer#12
Open
julianmesa-gitkraken wants to merge 38 commits intonodegit:libgit-nextfrom
Open
Fix leak tag create from buffer#12julianmesa-gitkraken wants to merge 38 commits intonodegit:libgit-nextfrom
julianmesa-gitkraken wants to merge 38 commits intonodegit:libgit-nextfrom
Conversation
GitHub is removing support for the unauthenticated git protocol; test with the https protocol.
Provide individual file ownership checks for both the current user and the system user, as well as a combined current user and system user check.
Ensure that the repository directory is owned by the current user; this prevents us from opening configuration files that may have been created by an attacker.
Provide a mock for file ownership for testability.
Test that we prevent opening directories that are not owned by ourselves.
Pull the global configuration loader out of the symlink check so that it can be re-used.
Obey the `safe.directory` configuration variable if it is set in the global or system configuration. (Do not try to load this from the repository configuration - to avoid malicious repositories that then mark themselves as safe.)
Introduce the `GIT_OPT_SET_OWNER_VALIDATION` option, so that users can disable repository ownership validation.
Validate repository directory ownership (v1.3)
v1.3.1 release
…library' into libgit-next
…new' into libgit-next
It is a string array of the filters you want to disable in checkout
…USE_NSEC disabled
…s-on-no-nanoseconds-repos Fix degraded performance using GIT_USE_NSEC on repos cloned with GIT_USE_NSEC disabled
There is a typo, Instead comparing nanoseconds to zero the code is comparing seconds to zero
Fix the GIT_USE_NSEC performance fix
we want to build a partial stash from an index in the future, so some functions have been reworked to allow for this
code has been moved from `git_stash_save` into `git_stash_save_with_opts` in order to handle cases where we want to partially stash using options or stash normally without partially stashed paths specified
stash: partial stash specific files
If the tag already exists and we are not forcing overwrite we need to free ref_name buffer before return the "tag already exists" error.
ianhattendorf
force-pushed
the
libgit-next
branch
from
0ac7af7 to
efdaa4a
Compare
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
6 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.
If the tag already exists and we are not forcing overwrite we need to free ref_name buffer before return the "tag already exists" error.