git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <derrickstolee@github.com>
To: "Git Mailing List" <git@vger.kernel.org>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Taylor Blau" <me@ttaylorr.com>,
	"Emily Shaffer" <emilyshaffer@google.com>,
	"Glen Choo" <chooglen@google.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Christian Couder" <christian.couder@gmail.com>
Subject: Re: [Discussion] What is Git's Security Boundary?
Date: Mon, 16 May 2022 10:13:45 -0400	[thread overview]
Message-ID: <daadac3e-d4c2-431f-a0bd-d8734d4424d8@github.com> (raw)
In-Reply-To: <6af83767-576b-75c4-c778-0284344a8fe7@github.com>

On 4/26/2022 1:00 PM, Derrick Stolee wrote:
> I've been having a few discussions internally and externally with folks
> about the 2.35.2 release and the safe.directory config value. After
> stumbling a little with a too-technical proposal, I (along with Taylor)
> figured out that I was jumping into "solutions" mode without first talking
> about the problem and agreeing on common language there.

> I'm hoping to start a conversation in this thread about "What is Git's
> security boundary?" so we can have an established base to work from for
> future security incidents or protections.

I'm back from a vacation, and haven't seen any response to this message.

I thought this would be an interesting topic that would create a lot of
valuable discussion, but that has not happened. I have a few ideas of why
that could be:

1. It's long, so readers put if off until it fell off the end of their
   inboxes.

2. The fixes for 2.36.1 have been taking priority.

3. There are no patches, so I should submit code if I want concrete
   feedback.

4. I'm so off base that it's not even worth replying.

Of course, it could be a combination of these or any number of other
things.

I'm sending this email as a hopeful ping that this topic could use some
feedback. I'm looking forward to your ideas.

Thanks,
-Stolee

  reply	other threads:[~2022-05-16 14:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 17:00 [Discussion] What is Git's Security Boundary? Derrick Stolee
2022-05-16 14:13 ` Derrick Stolee [this message]
2022-05-16 14:38   ` rsbecker
2022-05-20 17:23     ` Derrick Stolee
2022-05-17 12:55 ` Ævar Arnfjörð Bjarmason
2022-05-20 17:53   ` Derrick Stolee
2022-05-21 10:22     ` Æ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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=daadac3e-d4c2-431f-a0bd-d8734d4424d8@github.com \
    --to=derrickstolee@github.com \
    --cc=avarab@gmail.com \
    --cc=chooglen@google.com \
    --cc=christian.couder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    /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).