From: Sitaram Chamarty <sitaramc@gmail.com>
To: Guido Vranken <guidovranken@gmail.com>, git@vger.kernel.org
Subject: Re: Where to report security vulnerabilities in git?
Date: Mon, 24 Aug 2015 09:43:22 +0530 [thread overview]
Message-ID: <55DA99E2.7090707@gmail.com> (raw)
In-Reply-To: <CAO5O-EKaarYDBd-cpVvKVXTWfKm10ttqd3A6wNe2cXGriGux1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On 08/22/2015 04:25 AM, Guido Vranken wrote:
> List,
>
> I would like to report security vulnerabilities in git. Due to the
> sensitive nature of security-impacting bugs I would like to know if
> there's a dedicated e-mail address for this, so that the issues at
> play can be patched prior to a coordinated public disclosure of the
> germane exploitation details. I did find an older thread in the
> archive addressing this question (
> http://thread.gmane.org/gmane.comp.version-control.git/260328/ ), but
> because I'm unsure if those e-mail addresses are still relevant, I'm
> asking again.
If it has anything to do with remote access (via ssh or http) please
copy me also. I wrote/write/maintain gitolite, which is a reasonably
successful access control system for git servers.
regards
sitaram
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-08-24 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 22:55 Where to report security vulnerabilities in git? Guido Vranken
2015-08-22 0:02 ` Stefan Beller
2015-08-22 0:16 ` Junio C Hamano
2015-08-24 4:13 ` 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=55DA99E2.7090707@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=guidovranken@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.