From: "Matheus Valadares via GitGitGadget" <gitgitgadget@gmail.com> To: git@vger.kernel.org Cc: gitster@pobox.com, me@ttaylorr.com, johannes.schindelin@gmx.de, Derrick Stolee <derrickstolee@github.com>, Matheus Valadares <me@m28.io> Subject: [PATCH 2/3] setup: fix safe.directory key not being checked Date: Wed, 13 Apr 2022 15:32:30 +0000 [thread overview] Message-ID: <8a06688c121195f21472e3e49efd2b034b1537fc.1649863951.git.gitgitgadget@gmail.com> (raw) In-Reply-To: <pull.1215.git.1649863951.gitgitgadget@gmail.com> From: Matheus Valadares <me@m28.io> It seems that nothing is ever checking to make sure the safe directories in the configs actually have the key safe.directory, so some unrelated config that has a value with a certain directory would also make it a safe directory. Signed-off-by: Matheus Valadares <me@m28.io> Signed-off-by: Derrick Stolee <derrickstolee@github.com> --- setup.c | 3 +++ t/t0033-safe-directory.sh | 5 +++++ 2 files changed, 8 insertions(+) diff --git a/setup.c b/setup.c index f54f449008a..a995c359c32 100644 --- a/setup.c +++ b/setup.c @@ -1100,6 +1100,9 @@ static int safe_directory_cb(const char *key, const char *value, void *d) { struct safe_directory_data *data = d; + if (strcmp(key, "safe.directory")) + return 0; + if (!value || !*value) data->is_safe = 0; else { diff --git a/t/t0033-safe-directory.sh b/t/t0033-safe-directory.sh index 9380ff3d017..6f33c0dfefa 100755 --- a/t/t0033-safe-directory.sh +++ b/t/t0033-safe-directory.sh @@ -21,6 +21,11 @@ test_expect_success 'safe.directory does not match' ' expect_rejected_dir ' +test_expect_success 'path exist as different key' ' + git config --global foo.bar "$(pwd)" && + expect_rejected_dir +' + test_expect_success 'safe.directory matches' ' git config --global --add safe.directory "$(pwd)" && git status -- gitgitgadget
next prev parent reply other threads:[~2022-04-13 15:32 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 15:32 [PATCH 0/3] Updates to the safe.directory config option Derrick Stolee via GitGitGadget 2022-04-13 15:32 ` [PATCH 1/3] t0033: add tests for safe.directory Derrick Stolee via GitGitGadget 2022-04-13 16:24 ` Junio C Hamano 2022-04-13 16:29 ` Derrick Stolee 2022-04-13 19:16 ` Ævar Arnfjörð Bjarmason 2022-04-13 19:46 ` Junio C Hamano 2022-04-13 19:52 ` Derrick Stolee 2022-04-13 15:32 ` Matheus Valadares via GitGitGadget [this message] 2022-04-13 16:34 ` [PATCH 2/3] setup: fix safe.directory key not being checked Junio C Hamano 2022-04-13 15:32 ` [PATCH 3/3] setup: opt-out of check with safe.directory=* Derrick Stolee via GitGitGadget 2022-04-13 16:40 ` Junio C Hamano 2022-04-13 16:15 ` [PATCH 0/3] Updates to the safe.directory config option Junio C Hamano 2022-04-13 16:25 ` Derrick Stolee 2022-04-13 16:44 ` Junio C Hamano 2022-04-13 20:27 ` Junio C Hamano 2022-04-13 21:25 ` Taylor Blau 2022-04-13 21:45 ` Junio C Hamano 2022-04-27 17:06 ` [PATCH 0/3] t0033-safe-directory: test improvements and a documentation clarification SZEDER Gábor 2022-04-27 17:06 ` [PATCH 1/3] t0033-safe-directory: check the error message without matching the trash dir SZEDER Gábor 2022-05-09 22:27 ` Taylor Blau 2022-05-10 6:04 ` Carlo Marcelo Arenas Belón 2022-04-27 17:06 ` [PATCH 2/3] t0033-safe-directory: check when 'safe.directory' is ignored SZEDER Gábor 2022-04-27 20:37 ` Junio C Hamano 2022-04-29 16:12 ` Derrick Stolee 2022-04-29 17:57 ` Junio C Hamano 2022-04-29 19:06 ` SZEDER Gábor 2022-04-29 19:19 ` Derrick Stolee 2022-05-10 18:33 ` SZEDER Gábor 2022-05-10 19:55 ` Taylor Blau 2022-05-10 20:06 ` Carlo Marcelo Arenas Belón 2022-05-10 20:11 ` Taylor Blau 2022-05-10 20:18 ` Eric Sunshine 2022-04-27 17:06 ` [PATCH 3/3] safe.directory: document and check that it's ignored in the environment SZEDER Gábor 2022-04-27 20:42 ` Junio C Hamano 2022-04-27 20:49 ` Junio C Hamano 2022-04-29 16:13 ` Derrick Stolee 2022-05-09 21:39 ` SZEDER Gábor 2022-05-09 21:45 ` Junio C Hamano 2022-05-10 18:48 ` SZEDER Gábor
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=8a06688c121195f21472e3e49efd2b034b1537fc.1649863951.git.gitgitgadget@gmail.com \ --to=gitgitgadget@gmail.com \ --cc=derrickstolee@github.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=johannes.schindelin@gmx.de \ --cc=me@m28.io \ --cc=me@ttaylorr.com \ --subject='Re: [PATCH 2/3] setup: fix safe.directory key not being checked' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).