git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Adam Bannister <adam.bannister@portswigger.net>
Cc: git@vger.kernel.org
Subject: Re: Media query - Git flaw
Date: Wed, 15 Apr 2020 08:19:18 -0700	[thread overview]
Message-ID: <xmqqwo6g7p55.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAJQu+bp9SrzaMBuMv1UC8y8rJGn15MAsVogSCm_DNDKRMji1+Q@mail.gmail.com> (Adam Bannister's message of "Wed, 15 Apr 2020 11:46:04 +0100")

Adam Bannister <adam.bannister@portswigger.net> writes:

> How did the disclosure and patching process go?

I guess "Just like any other project" would be enough for you to
understand, given what you write and where ;-)

A security researcher discloses a possible vulnerability to the
git-security mailing list, which is a closed list.  On the list,
there are developers with relatively high familiarity with the
entire codebase, and there are those who are responsible for
managing binary packaging of the software to various distributions.

We prepare the fix.  We review the fix.  We repeat until we agree
that the proposed fix is what we want to deliver.

We arrange the coordinated disclosure and release among distro
people and other stakeholders.

All of the above have to be done behind public.

Then we go public at the same time.  It happened at 1100 US/Pacific
on Apr 14th, 2020.  For this one, as the fix itself was relatively
straight-forward, the time it took between the initial contact and
the release was spent mostly to wait for the slowest partcipant in
the coordinated disclosure process (obviously I won't name names).

> What is your advice to Git users?

Release is announced and users are urged to upgrade, like you wrote
on your article at The Daily Swig.

  reply	other threads:[~2020-04-15 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 10:46 Media query - Git flaw Adam Bannister
2020-04-15 15:19 ` Junio C Hamano [this message]
2020-04-15 15:47   ` Jeff King
2020-04-21  8:46     ` Adam Bannister

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=xmqqwo6g7p55.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=adam.bannister@portswigger.net \
    --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).