From: Jeff Law <law@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
"Charles A. Morris" <cmorris@cs.odu.edu>
Cc: overseers@gcc.gnu.org, charlesmorris@gmail.com
Subject: Re: reporting a security issue in gcc / bugzilla account
Date: Thu, 04 May 2017 14:41:00 -0000 [thread overview]
Message-ID: <ba4e28d0-3693-913d-4847-382605c5f009@redhat.com> (raw)
In-Reply-To: <20170503215838.GA97187@elastic.org>
On 05/03/2017 03:58 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> I'd like to have a gcc bugzilla account.
>
> Done, enjoy.
>
>> That said, I have found a few security issues in gcc.
>> Is there a way to safely report these through bugzilla?
>> What is the preferred point of contact for these types of issues?
>
> I am not aware of any sort of confidential security contact for gcc.
> Unless you have some reason to believe it's a non-trivial severity
> (CVSS score), maybe might just as well post it publicly.
Right. We really don't bother with embargos and the like.
Jeff
prev parent reply other threads:[~2017-05-04 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 21:25 Charles A. Morris
2017-05-03 21:58 ` Frank Ch. Eigler
2017-05-04 14:41 ` Jeff Law [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=ba4e28d0-3693-913d-4847-382605c5f009@redhat.com \
--to=law@redhat.com \
--cc=charlesmorris@gmail.com \
--cc=cmorris@cs.odu.edu \
--cc=fche@elastic.org \
--cc=overseers@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).