From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: FW: [oss-security] accepting new members to (linux-)distros lists
Date: Sat, 01 Jul 2017 15:26:20 +0200 [thread overview]
Message-ID: <87a84offur.fsf@gnu.org> (raw)
In-Reply-To: <20170628213609.GA14802@jasmine.lan> (Leo Famulari's message of "Wed, 28 Jun 2017 17:36:09 -0400")
Hello,
Leo Famulari <leo@famulari.name> skribis:
> I've seen some members of Guix express doubts about the utility of
> private discussion forums like linux-distros, and I'm sympathetic.
>
> In fact, even without early notification, we are usually shipping
> security updates for embargoed issues within 24 hours of public
> disclosure, and usually within a few hours. And for non-embargoed
> issues, we are shipping fixes earlier than the major distros very often.
> I read the "security update round-ups" on LWN, and typically they are
> full of bugs we already fixed. So, perhaps it wouldn't make a big
> difference in most cases.
>
> But, the "Stack Clash" issues took us by surprise and we spent a few
> days writing and testing our fixes. We are committed to supporting
> 32-bit platforms where these bugs are apparently easy to exploit.
> Without access to the exploits or detailed discussion, it was very
> difficult to know if our fixes actually worked. So, we could have
> responded more quickly and effectively with early notice.
>
> What do people think? Is anyone else interested in applying to join this
> mailing list? Is anyone else willing to stick to the rules and to
> participate?
Like you say, you (and Mark and others) have been doing excellent work
already without being on that list, but I agree that the early notice
could help in some cases. So overall I think being on linux-distros is
a good idea, and it seems like we meet the criteria.
The real question is about our commitment to contribute back.
Presumably only one or two of us would be on that list, so they would
largely have that responsibility individually, even if the rest of us
could of course help out as far as the embargo etc. permits.
Long story short, I would be super happy if you or Mark were on that
list.
How do you feel about it?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-07-01 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 21:36 FW: [oss-security] accepting new members to (linux-)distros lists Leo Famulari
2017-06-28 22:45 ` ng0
2017-06-29 4:48 ` Alex Vong
2017-07-07 19:18 ` Leo Famulari
2017-07-10 15:56 ` Ludovic Courtès
2017-06-29 19:27 ` Marius Bakke
2017-07-01 13:26 ` Ludovic Courtès [this message]
2017-07-05 17:33 ` Mark H Weaver
2017-07-07 19:38 ` Leo Famulari
2017-07-10 15:53 ` Ludovic Courtès
2017-07-10 17:24 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a84offur.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).