From: Junio C Hamano <gitster@pobox.com> To: Philip Oakley <philipoakley@iee.email> Cc: "Glen Choo" <chooglen@google.com>, "Taylor Blau" <me@ttaylorr.com>, git@vger.kernel.org, "Emily Shaffer" <emilyshaffer@google.com>, justin@justinsteven.com, "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, "Derrick Stolee" <derrickstolee@github.com>, "brian m. carlson" <sandals@crustytoothpaste.net>, rsbecker@nexbridge.com Subject: Re: Bare repositories in the working tree are a security risk Date: Mon, 02 May 2022 11:50:40 -0700 [thread overview] Message-ID: <xmqqr15bydj3.fsf@gitster.g> (raw) In-Reply-To: <324301af-4ad3-739c-25bb-1ddbe069eb3e@iee.email> Philip Oakley <philipoakley@iee.email> writes: > Can I check that storing bundles (of other repos) within a repository is > considered reasonably safe? I think the threat model we are protecting against is that we shouldn't have to worry about "git clone" and then "cd" into the hierarchy. If you did "make" in there and their Makefile (or "runme.sh" shipped as part of the tree) is malicious, that is not something we can solve. So, I would say it is safe to have a bundle, as in its statinary state it does not actively do anything bad, even when you did "ls" in a directory that stores it. > I have been looking at how Git's documentation could carry with it small > exemplar repositories that cover the commit hierarchies shown in the > various man pages to allow users to see, explore and understand the man > page examples. I'd settled on bundles as a reasonable compromise, with > the exemplar repositories being generated via the test suite > (obviously). With the recent focus on security issues, I thought it > worth asking now. A bundle would be an OK vehicle. This depends on the size of the sample project, but another that may be more suitable may be to create the repository on the fly in the "test suite" you were planning to use to extract from the bundle.
prev parent reply other threads:[~2022-05-02 18:51 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 22:43 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 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 [this message]
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=xmqqr15bydj3.fsf@gitster.g \ --to=gitster@pobox.com \ --cc=Johannes.Schindelin@gmx.de \ --cc=avarab@gmail.com \ --cc=chooglen@google.com \ --cc=derrickstolee@github.com \ --cc=emilyshaffer@google.com \ --cc=git@vger.kernel.org \ --cc=justin@justinsteven.com \ --cc=me@ttaylorr.com \ --cc=philipoakley@iee.email \ --cc=rsbecker@nexbridge.com \ --cc=sandals@crustytoothpaste.net \ --subject='Re: Bare repositories in the working tree are a security risk' \ /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
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).