From: Sitaram Chamarty <sitaramc@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>,
Hugh Davenport <hugh@davenport.net.nz>
Cc: git@vger.kernel.org
Subject: Re: Where is the best place to report a security vulnerability in git?
Date: Thu, 27 Nov 2014 09:02:08 +0530 [thread overview]
Message-ID: <54769B38.30708@gmail.com> (raw)
In-Reply-To: <20141127012053.GU6527@google.com>
On 11/27/2014 06:50 AM, Jonathan Nieder wrote:
> 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.
Hi Hugh,
I maintain a somewhat widely used access control program for remote
access to git, so I'm interested also.
Gitolite [1] and similar systems provide access control for git repos.
There's a very good chance that something which is not a concern for
"local" use, could become an attack vector if enabled through gitolite.
Hence my interest, and my request that I be copied.
Jonathan/Junio/Jeff: if such a mailing list does happen please consider
adding me into it.
regards
sitaram
[1]: https://gitolite.com
prev parent reply other threads:[~2014-11-27 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 0:49 Where is the best place to report a security vulnerability in git? Hugh Davenport
2014-11-27 1:20 ` Jonathan Nieder
2014-11-27 2:04 ` Hugh Davenport
2014-11-27 3:32 ` Sitaram Chamarty [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=54769B38.30708@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=hugh@davenport.net.nz \
--cc=jrnieder@gmail.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).