git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Where is the best place to report a security vulnerability in git?

From
Hugh Davenport <hugh@davenport.net.nz>
Date
Nov 27, 2014, 02:04 UTC
Message-ID
<760122B3-B9D5-4574-9B0D-1EDF95ED53C0@davenport.net.nz>
In-Reply-To
<20141127012053.GU6527@google.com>
Thanks. Will send a report their way soon
On 27 November 2014 2:20:53 pm NZDT, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 14 quoted lines
>Hi Hugh,
>
>Hugh Davenport wrote:
>
>> Where is the best place to report a security vulnerability in git?
>
>Current practice is to contact Junio C Hamano <gitster@pobox.com>.
>Cc-ing Jeff King <peff@peff.net> isn't a bad idea while at it.
>
>We should probably set up a mailing list to make this more obvious,
>but that's what we have today.
>
>Thanks,
>Jonathan
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Previous: Jonathan NiederNext: Sitaram Chamarty
Message 3 of 4 in “Where is the best place to report a security vulnerability in git?”
  1. Hugh DavenportNov 27, 2014
  2. Jonathan NiederNov 27, 2014
  3. Hugh DavenportNov 27, 2014
  4. Sitaram ChamartyNov 27, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.