From: "Glen Choo via GitGitGadget" <gitgitgadget@gmail.com> To: git@vger.kernel.org Cc: Taylor Blau <me@ttaylorr.com>, "brian m. carlson" <sandals@crustytoothpaste.net>, Derrick Stolee <derrickstolee@github.com>, Junio C Hamano <gitster@pobox.com>, Emily Shaffer <emilyshaffer@google.com>, Glen Choo <chooglen@google.com>, Glen Choo <chooglen@google.com> Subject: [PATCH v2 1/2] setup.c: make bare repo discovery optional Date: Fri, 13 May 2022 23:37:37 +0000 [thread overview] Message-ID: <22b10bf9da8ccf4ae4da634aadfdaff5ee7a3508.1652485058.git.gitgitgadget@gmail.com> (raw) In-Reply-To: <pull.1261.v2.git.git.1652485058.gitgitgadget@gmail.com> From: Glen Choo <chooglen@google.com> Add a config variable, `discovery.bare`, that tells Git whether or not it should work with the bare repository it has discovered i.e. Git will die() if it discovers a bare repository, but it is not allowed by `discovery.bare`. This only affects repository discovery, thus it has no effect if discovery was not done (e.g. `--git-dir` was passed). This is motivated by the fact that some workflows don't use bare repositories at all, and users may prefer to opt out of bare repository discovery altogether: - An easy assumption for a user to make is that Git commands run anywhere inside a repository's working tree will use the same repository. However, if the working tree contains a bare repository below the root-level (".git" is preferred at the root-level), any operations inside that bare repository use the bare repository instead. In the worst case, attackers can use this confusion to trick users into running arbitrary code (see [1] for a deeper discussion). But even in benign situations (e.g. a user renames ".git/" to ".git.old/" and commits it for archival purposes), disabling bare repository discovery can be a simpler mode of operation (e.g. because the user doesn't actually want to use ".git.old/") [2]. - Git won't "accidentally" recognize a directory that wasn't meant to be a bare repository, but happens to resemble one. While such accidents are probably very rare in practice, this lets users reduce the chance to zero. This config is an enum of: - ["always"|(unset)]: always recognize bare repositories (like Git does today) - "never": never recognize bare repositories More values are expected to be added later, and the default is expected to change (i.e. to something other than "always"). [1]: https://lore.kernel.org/git/kl6lsfqpygsj.fsf@chooglen-macbookpro.roam.corp.google.com [2]: I don't personally know anyone who does this as part of their normal workflow, but a cursory search on GitHub suggests that there is a not insubstantial number of people who munge ".git" in order to store its contents. https://github.com/search?l=&o=desc&p=1&q=ref+size%3A%3C1000+filename%3AHEAD&s=indexed&type=Code (aka search for the text "ref", size:<1000, filename:HEAD) Signed-off-by: Glen Choo <chooglen@google.com> WIP setup.c: make discovery.bare die on failure Signed-off-by: Glen Choo <chooglen@google.com> --- Documentation/config/discovery.txt | 24 +++++++++++ setup.c | 66 +++++++++++++++++++++++++++++- t/t0034-discovery-bare.sh | 59 ++++++++++++++++++++++++++ 3 files changed, 148 insertions(+), 1 deletion(-) create mode 100644 Documentation/config/discovery.txt create mode 100755 t/t0034-discovery-bare.sh diff --git a/Documentation/config/discovery.txt b/Documentation/config/discovery.txt new file mode 100644 index 00000000000..761cabe6e70 --- /dev/null +++ b/Documentation/config/discovery.txt @@ -0,0 +1,24 @@ +discovery.bare:: + Specifies what kinds of directories Git can recognize as a bare + repository when looking for the repository (aka repository + discovery). This has no effect if repository discovery is not + performed e.g. the path to the repository is set via `--git-dir` + (see linkgit:git[1]). ++ +This config setting is only respected when specified in a system or global +config, not when it is specified in a repository config or via the command +line option `-c discovery.bare=<value>`. ++ +The currently supported values are `always` (Git always recognizes bare +repositories) and `never` (Git never recognizes bare repositories). +This defaults to `always`, but this default is likely to change. ++ +If your workflow does not rely on bare repositories, it is recommended that +you set this value to `never`. This makes repository discovery easier to +reason about and prevents certain types of security and non-security +problems, such as: + +* `git clone`-ing a repository containing a malicious bare repository + inside it. +* Git recognizing a directory that isn't meant to be a bare repository, + but happens to look like one. diff --git a/setup.c b/setup.c index a7b36f3ffbf..cee01d86f0c 100644 --- a/setup.c +++ b/setup.c @@ -10,6 +10,13 @@ static int inside_git_dir = -1; static int inside_work_tree = -1; static int work_tree_config_is_bogus; +enum discovery_bare_config { + DISCOVERY_BARE_UNKNOWN = -1, + DISCOVERY_BARE_NEVER = 0, + DISCOVERY_BARE_ALWAYS, +}; +static enum discovery_bare_config discovery_bare_config = + DISCOVERY_BARE_UNKNOWN; static struct startup_info the_startup_info; struct startup_info *startup_info = &the_startup_info; @@ -1133,6 +1140,52 @@ static int ensure_valid_ownership(const char *path) return data.is_safe; } +static int discovery_bare_cb(const char *key, const char *value, void *d) +{ + if (strcmp(key, "discovery.bare")) + return 0; + + if (!strcmp(value, "never")) { + discovery_bare_config = DISCOVERY_BARE_NEVER; + return 0; + } + if (!strcmp(value, "always")) { + discovery_bare_config = DISCOVERY_BARE_ALWAYS; + return 0; + } + return -1; +} + +static int check_bare_repo_allowed(void) +{ + if (discovery_bare_config == DISCOVERY_BARE_UNKNOWN) { + read_very_early_config(discovery_bare_cb, NULL); + /* We didn't find a value; use the default. */ + if (discovery_bare_config == DISCOVERY_BARE_UNKNOWN) + discovery_bare_config = DISCOVERY_BARE_ALWAYS; + } + switch (discovery_bare_config) { + case DISCOVERY_BARE_NEVER: + return 0; + case DISCOVERY_BARE_ALWAYS: + return 1; + default: + BUG("invalid discovery_bare_config %d", discovery_bare_config); + } +} + +static const char *discovery_bare_config_to_string(void) +{ + switch (discovery_bare_config) { + case DISCOVERY_BARE_NEVER: + return "never"; + case DISCOVERY_BARE_ALWAYS: + return "always"; + default: + BUG("invalid discovery_bare_config %d", discovery_bare_config); + } +} + enum discovery_result { GIT_DIR_NONE = 0, GIT_DIR_EXPLICIT, @@ -1142,7 +1195,8 @@ enum discovery_result { GIT_DIR_HIT_CEILING = -1, GIT_DIR_HIT_MOUNT_POINT = -2, GIT_DIR_INVALID_GITFILE = -3, - GIT_DIR_INVALID_OWNERSHIP = -4 + GIT_DIR_INVALID_OWNERSHIP = -4, + GIT_DIR_DISALLOWED_BARE = -5 }; /* @@ -1239,6 +1293,8 @@ static enum discovery_result setup_git_directory_gently_1(struct strbuf *dir, } if (is_git_directory(dir->buf)) { + if (!check_bare_repo_allowed()) + return GIT_DIR_DISALLOWED_BARE; if (!ensure_valid_ownership(dir->buf)) return GIT_DIR_INVALID_OWNERSHIP; strbuf_addstr(gitdir, "."); @@ -1385,6 +1441,14 @@ const char *setup_git_directory_gently(int *nongit_ok) } *nongit_ok = 1; break; + case GIT_DIR_DISALLOWED_BARE: + if (!nongit_ok) { + die(_("cannot use bare repository '%s' (discovery.bare is '%s')"), + dir.buf, + discovery_bare_config_to_string()); + } + *nongit_ok = 1; + break; case GIT_DIR_NONE: /* * As a safeguard against setup_git_directory_gently_1 returning diff --git a/t/t0034-discovery-bare.sh b/t/t0034-discovery-bare.sh new file mode 100755 index 00000000000..9c774872c4e --- /dev/null +++ b/t/t0034-discovery-bare.sh @@ -0,0 +1,59 @@ +#!/bin/sh + +test_description='verify discovery.bare checks' + +. ./test-lib.sh + +pwd="$(pwd)" + +expect_allowed () { + git rev-parse --absolute-git-dir >actual && + echo "$pwd/outer-repo/bare-repo" >expected && + test_cmp expected actual +} + +expect_rejected () { + test_must_fail git rev-parse --absolute-git-dir 2>err && + grep "discovery.bare" err +} + +test_expect_success 'setup bare repo in worktree' ' + git init outer-repo && + git init --bare outer-repo/bare-repo +' + +test_expect_success 'discovery.bare unset' ' + ( + cd outer-repo/bare-repo && + expect_allowed && + cd refs/ && + expect_allowed + ) +' + +test_expect_success 'discovery.bare=always' ' + git config --global discovery.bare always && + ( + cd outer-repo/bare-repo && + expect_allowed && + cd refs/ && + expect_allowed + ) +' + +test_expect_success 'discovery.bare=never' ' + git config --global discovery.bare never && + ( + cd outer-repo/bare-repo && + expect_rejected && + cd refs/ && + expect_rejected + ) && + ( + GIT_DIR=outer-repo/bare-repo && + export GIT_DIR && + expect_allowed + ) +' + +test_done -- gitgitgadget
next prev parent reply other threads:[~2022-05-13 23:48 UTC|newest] Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-06 18:30 [PATCH] [RFC] " Glen Choo via GitGitGadget 2022-05-06 20:33 ` Junio C Hamano 2022-05-09 21:42 ` Taylor Blau 2022-05-09 22:54 ` Junio C Hamano 2022-05-09 23:57 ` Taylor Blau 2022-05-10 0:23 ` Junio C Hamano 2022-05-10 22:00 ` Glen Choo 2022-05-13 23:37 ` [PATCH v2 0/2] " Glen Choo via GitGitGadget 2022-05-13 23:37 ` Glen Choo via GitGitGadget [this message] 2022-05-16 18:12 ` [PATCH v2 1/2] " Glen Choo 2022-05-16 18:46 ` Derrick Stolee 2022-05-16 22:25 ` Taylor Blau 2022-05-17 20:24 ` Glen Choo 2022-05-17 21:51 ` Glen Choo 2022-05-13 23:37 ` [PATCH v2 2/2] setup.c: learn discovery.bareRepository=cwd Glen Choo via GitGitGadget 2022-05-16 18:49 ` Derrick Stolee 2022-05-16 16:40 ` [PATCH v2 0/2] setup.c: make bare repo discovery optional Junio C Hamano 2022-05-16 18:36 ` Glen Choo 2022-05-16 19:16 ` Junio C Hamano 2022-05-16 20:27 ` Glen Choo 2022-05-16 22:16 ` Junio C Hamano 2022-05-16 16:43 ` Junio C Hamano 2022-05-16 19:07 ` Derrick Stolee 2022-05-16 22:43 ` Taylor Blau 2022-05-16 23:19 ` Junio C Hamano 2022-05-17 18:56 ` Glen Choo 2022-05-27 21:09 ` [PATCH v3 0/5] config: introduce discovery.bare and protected config Glen Choo via GitGitGadget 2022-05-27 21:09 ` [PATCH v3 1/5] Documentation: define protected configuration Glen Choo via GitGitGadget 2022-05-27 23:29 ` Junio C Hamano 2022-06-02 12:42 ` Derrick Stolee 2022-06-02 16:53 ` Junio C Hamano 2022-06-02 17:39 ` Glen Choo 2022-06-03 15:57 ` Glen Choo 2022-05-27 21:09 ` [PATCH v3 2/5] config: read protected config with `git_protected_config()` Glen Choo via GitGitGadget 2022-05-28 0:28 ` Junio C Hamano 2022-05-31 17:43 ` Glen Choo 2022-06-01 15:58 ` Junio C Hamano 2022-06-02 12:56 ` Derrick Stolee 2022-05-27 21:09 ` [PATCH v3 3/5] setup.c: create `discovery.bare` Glen Choo via GitGitGadget 2022-05-28 0:59 ` Junio C Hamano 2022-06-02 13:11 ` Derrick Stolee 2022-05-27 21:09 ` [PATCH v3 4/5] config: include "-c" in protected config Glen Choo via GitGitGadget 2022-06-02 13:15 ` Derrick Stolee 2022-05-27 21:09 ` [PATCH v3 5/5] upload-pack: make uploadpack.packObjectsHook protected Glen Choo via GitGitGadget 2022-06-02 13:18 ` Derrick Stolee 2022-06-07 20:57 ` [PATCH v4 0/5] config: introduce discovery.bare and protected config Glen Choo via GitGitGadget 2022-06-07 20:57 ` [PATCH v4 1/5] Documentation/git-config.txt: add SCOPES section Glen Choo via GitGitGadget 2022-06-07 20:57 ` [PATCH v4 2/5] Documentation: define protected configuration Glen Choo via GitGitGadget 2022-06-22 21:58 ` Jonathan Tan 2022-06-23 18:21 ` Glen Choo 2022-06-07 20:57 ` [PATCH v4 3/5] config: read protected config with `git_protected_config()` Glen Choo via GitGitGadget 2022-06-07 22:49 ` Junio C Hamano 2022-06-08 0:22 ` Glen Choo 2022-06-07 20:57 ` [PATCH v4 4/5] safe.directory: use git_protected_config() Glen Choo via GitGitGadget 2022-06-07 20:57 ` [PATCH v4 5/5] setup.c: create `discovery.bare` Glen Choo via GitGitGadget 2022-06-07 21:37 ` Glen Choo 2022-06-22 22:03 ` [PATCH v4 0/5] config: introduce discovery.bare and protected config Jonathan Tan 2022-06-23 17:13 ` Glen Choo 2022-06-23 18:32 ` Junio C Hamano 2022-06-27 17:34 ` Glen Choo 2022-06-27 18:19 ` Glen Choo 2022-06-27 18:36 ` [PATCH v5 " Glen Choo via GitGitGadget 2022-06-27 18:36 ` [PATCH v5 1/5] Documentation/git-config.txt: add SCOPES section Glen Choo via GitGitGadget 2022-06-27 18:36 ` [PATCH v5 2/5] Documentation: define protected configuration Glen Choo via GitGitGadget 2022-06-27 18:36 ` [PATCH v5 3/5] config: learn `git_protected_config()` Glen Choo via GitGitGadget 2022-06-27 18:36 ` [PATCH v5 4/5] safe.directory: use git_protected_config() Glen Choo via GitGitGadget 2022-06-27 18:36 ` [PATCH v5 5/5] setup.c: create `discovery.bare` Glen Choo via GitGitGadget 2022-06-30 13:20 ` Ævar Arnfjörð Bjarmason 2022-06-30 17:28 ` Glen Choo 2022-06-30 18:13 ` [PATCH v6 0/5] config: introduce discovery.bare and protected config Glen Choo via GitGitGadget 2022-06-30 18:13 ` [PATCH v6 1/5] Documentation/git-config.txt: add SCOPES section Glen Choo via GitGitGadget 2022-06-30 22:32 ` Taylor Blau 2022-06-30 18:13 ` [PATCH v6 2/5] Documentation: define protected configuration Glen Choo via GitGitGadget 2022-06-30 23:49 ` Taylor Blau 2022-06-30 18:13 ` [PATCH v6 3/5] config: learn `git_protected_config()` Glen Choo via GitGitGadget 2022-06-30 18:13 ` [PATCH v6 4/5] safe.directory: use git_protected_config() Glen Choo via GitGitGadget 2022-06-30 18:13 ` [PATCH v6 5/5] setup.c: create `discovery.bare` Glen Choo via GitGitGadget 2022-06-30 22:13 ` [PATCH v6 0/5] config: introduce discovery.bare and protected config Taylor Blau 2022-06-30 23:07 ` Ævar Arnfjörð Bjarmason
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=22b10bf9da8ccf4ae4da634aadfdaff5ee7a3508.1652485058.git.gitgitgadget@gmail.com \ --to=gitgitgadget@gmail.com \ --cc=chooglen@google.com \ --cc=derrickstolee@github.com \ --cc=emilyshaffer@google.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=me@ttaylorr.com \ --cc=sandals@crustytoothpaste.net \ --subject='Re: [PATCH v2 1/2] setup.c: make bare repo discovery optional' \ /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).