From: Ed Tanous <edtanous@google.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: openbmc@lists.ozlabs.org,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
Joseph Reynolds <jrey@linux.ibm.com>
Subject: Re: Security Working Group meeting - Wednesday August 4 - results
Date: Wed, 4 Aug 2021 16:57:52 -0700 [thread overview]
Message-ID: <CAH2-KxBqzCr--LN93P=OsmorDPkbgzDxyxpSGckzFX7MAv96eA@mail.gmail.com> (raw)
In-Reply-To: <6aa885f5-6870-4ca7-b5b5-cfc9568f1f96@www.fastmail.com>
On Wed, Aug 4, 2021 at 4:48 PM Andrew Jeffery <andrew@aj.id.au> wrote:
>
>
>
> On Thu, 5 Aug 2021, at 06:19, Patrick Williams wrote:
> > On Wed, Aug 04, 2021 at 03:39:45PM -0500, Joseph Reynolds wrote:
> > > On 8/4/21 3:09 PM, Patrick Williams wrote:
> > > > On Wed, Aug 04, 2021 at 01:47:31PM -0500, Joseph Reynolds wrote:
> > > >
> > > >> 4 Surya set up a bugzilla within Intel and will administer it. Demo’d
> > > >> the database. We briefly examined the database fields and agreed it
> > > >> looks like a good start.
> > > >>
> > > > Once again I'll ask ***WHY***??!?
> > > >
> > > > https://lore.kernel.org/openbmc/YNzsE1ipYQR7yfDq@heinlein/
> > > > https://lore.kernel.org/openbmc/YPiK8xqFPJFZDa1+@heinlein/
> > > >
> > > > Can we please create a private Github repository and be done with this topic?
> > >
> > > I don't have any insight into how to resolve this question.
> > >
> > > From today's meeting: using bugzilla has advantages over github issues:
> > > - lets us define the fields we need: fix commitID, CVSS score, etc.
I'm also really not following this as a rationale for starting a
completely new server. This is easy enough to add on github in the
bug template.
> >
> > These are pretty minor when you could just add a comment template with this
> > information.
> >
> > > - has desirable access controls, specifically acess by the security
> > > respone tram plus we can add access for the problem submitter and the
> > > problem fixer
> >
> > So does Github.
+1
> >
> > ----
> >
> > I really don't think that some subset of the community should go off on their
> > own bug tracking system.
>
> +1
>
> I'm not aware of any effort to use Github security advisories so far. I
> think we should try that before burdening ourselves and any bug
> reporters with yet more disjoint bits of infrastructure (we already
> have the two mailing lists, discord, gerrit, and github).
+1
>
> Andrew
next prev parent reply other threads:[~2021-08-04 23:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 22:57 Security Working Group meeting - Wednesday August 4 Joseph Reynolds
2021-08-04 3:04 ` Patrick Williams
2021-08-04 3:22 ` Patrick Williams
2021-08-09 14:09 ` Security Working Group meeting - Wednesday August 4 - ibm-acf repo Joseph Reynolds
2021-08-04 3:28 ` Security Working Group meeting - Wednesday August 4 Patrick Williams
2021-08-04 18:43 ` Security Working Group meeting - Wednesday August 4 - all distro owners please review Joseph Reynolds
2021-08-04 18:47 ` Security Working Group meeting - Wednesday August 4 - results Joseph Reynolds
2021-08-04 20:09 ` Patrick Williams
2021-08-04 20:39 ` Joseph Reynolds
2021-08-04 20:49 ` Patrick Williams
2021-08-04 23:23 ` Patrick Williams
2021-08-06 17:10 ` Mihm, James
2021-08-04 23:47 ` Andrew Jeffery
2021-08-04 23:57 ` Ed Tanous [this message]
2021-08-05 13:55 ` Brad Bishop
2021-08-05 13:43 ` Brad Bishop
2021-08-05 15:54 ` Brad Bishop
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='CAH2-KxBqzCr--LN93P=OsmorDPkbgzDxyxpSGckzFX7MAv96eA@mail.gmail.com' \
--to=edtanous@google.com \
--cc=andrew@aj.id.au \
--cc=bradleyb@fuzziesquirrel.com \
--cc=jrey@linux.ibm.com \
--cc=openbmc@lists.ozlabs.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 NNTP newsgroup(s).