From: Richard Hansen <rhansen@bbn.com>
To: Git List <git@vger.kernel.org>
Subject: security vulnerability disclosure procedure?
Date: Sun, 20 Apr 2014 16:42:09 -0400 [thread overview]
Message-ID: <53543121.3000808@bbn.com> (raw)
Hi all,
I have discovered a minor security vulnerability. I could send the
patch to the mailing list, but I wanted someone else to take a look
first just to make sure it's minor enough that folks will think it's OK
to publicly announce.
Who should I send the patch to?
Thanks,
Richard
next reply other threads:[~2014-04-20 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 20:42 Richard Hansen [this message]
2014-04-21 18:07 ` security vulnerability disclosure procedure? Shawn Pearce
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=53543121.3000808@bbn.com \
--to=rhansen@bbn.com \
--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 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.