From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] fsck: detect bare repos in trees and warn
Date: Thu, 07 Apr 2022 08:20:37 -0700 [thread overview]
Message-ID: <xmqqzgkwudh6.fsf@gitster.g> (raw)
In-Reply-To: <20220406232231.47714-1-chooglen@google.com> (Glen Choo's message of "Wed, 6 Apr 2022 16:22:31 -0700")
Glen Choo <chooglen@google.com> writes:
> @@ -602,6 +605,12 @@ static int fsck_tree(const struct object_id *tree_oid,
> has_dotdot |= !strcmp(name, "..");
> has_dotgit |= is_hfs_dotgit(name) || is_ntfs_dotgit(name);
> has_zero_pad |= *(char *)desc.buffer == '0';
> + has_head |= !strcasecmp(name, "HEAD")
> + && (S_ISLNK(mode) || S_ISREG(mode));
> + has_refs_entry |= !strcasecmp(name, "refs")
> + && (S_ISLNK(mode) || S_ISDIR(mode));
Sorry, I know I am to blame, but I think it is wrong to insist
"refs" (and others) to be a directory. setup.c::is_git_directory()
only checks with access(X_OK). Also, if I am not mistaken, we plan
to take advantage of it and may make refs a regular file, for
example, to signal that the ref-files backend is unwelcome in the
repository. HEAD can be a symbolic link, not necessarily a regular
file. We do not create "refs" and "objects" as symbolic links
ourselves, but it is good to see that the code protects us against
such a directory with these entries being one.
> + has_objects_entry |= !strcasecmp(name, "objects")
> + && (S_ISLNK(mode) || S_ISDIR(mode));
>
> if (is_hfs_dotgitmodules(name) || is_ntfs_dotgitmodules(name)) {
> if (!S_ISLNK(mode))
> @@ -739,6 +748,16 @@ static int fsck_tree(const struct object_id *tree_oid,
> retval += report(options, tree_oid, OBJ_TREE,
> FSCK_MSG_TREE_NOT_SORTED,
> "not properly sorted");
> + /*
> + * Determine if this tree looks like a bare repository according
> + * to the rules of setup.c. If those are changed, this should be
> + * changed too.
> + */
> + if (has_head && has_refs_entry && has_objects_entry)
> + retval += report(options, tree_oid, OBJ_TREE,
> + FSCK_MSG_EMBEDDED_BARE_REPO,
> + "contains bare repository");
> +
> return retval;
> }
next prev parent reply other threads:[~2022-04-07 15:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 22:43 Bare repositories in the working tree are a security risk Glen Choo
2022-04-06 23:22 ` [PATCH] fsck: detect bare repos in trees and warn Glen Choo
2022-04-07 12:42 ` Johannes Schindelin
2022-04-07 13:21 ` Derrick Stolee
2022-04-07 14:14 ` Ævar Arnfjörð Bjarmason
2022-04-14 20:02 ` Glen Choo
2022-04-15 12:46 ` Ævar Arnfjörð Bjarmason
2022-04-07 15:11 ` Junio C Hamano
2022-04-13 22:24 ` Glen Choo
2022-04-07 13:12 ` Ævar Arnfjörð Bjarmason
2022-04-07 15:20 ` Junio C Hamano [this message]
2022-04-07 18:38 ` Bare repositories in the working tree are a security risk John Cai
2022-04-07 21:24 ` brian m. carlson
2022-04-07 21:53 ` Justin Steven
2022-04-07 22:10 ` brian m. carlson
2022-04-07 22:40 ` rsbecker
2022-04-08 5:54 ` Junio C Hamano
2022-04-14 0:03 ` Junio C Hamano
2022-04-14 0:04 ` Glen Choo
2022-04-13 23:44 ` Glen Choo
2022-04-13 20:37 ` Glen Choo
2022-04-13 23:36 ` Junio C Hamano
2022-04-14 16:41 ` Glen Choo
2022-04-14 17:35 ` Junio C Hamano
2022-04-14 18:19 ` Junio C Hamano
2022-04-15 21:33 ` Glen Choo
2022-04-15 22:17 ` Junio C Hamano
2022-04-16 0:52 ` Taylor Blau
2022-04-15 22:43 ` Glen Choo
2022-04-15 20:13 ` Junio C Hamano
2022-04-15 23:45 ` Glen Choo
2022-04-15 23:59 ` Glen Choo
2022-04-16 1:00 ` Taylor Blau
2022-04-16 1:18 ` Junio C Hamano
2022-04-16 1:30 ` Taylor Blau
2022-04-16 0:34 ` Glen Choo
2022-04-16 0:41 ` Glen Choo
2022-04-16 1:28 ` Taylor Blau
2022-04-21 18:25 ` Emily Shaffer
2022-04-21 18:29 ` Emily Shaffer
2022-04-21 18:47 ` Junio C Hamano
2022-04-21 18:54 ` Taylor Blau
2022-04-21 19:09 ` Taylor Blau
2022-04-21 21:01 ` Emily Shaffer
2022-04-21 21:22 ` Taylor Blau
2022-04-29 23:57 ` Glen Choo
2022-04-30 1:14 ` Taylor Blau
2022-05-02 19:39 ` Glen Choo
2022-05-02 14:05 ` Philip Oakley
2022-05-02 18:50 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzgkwudh6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).