public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [pre-glep] Security Project Structure
Date: Tue, 4 Dec 2018 17:23:24 -0500	[thread overview]
Message-ID: <1cd5f6d9-b71e-a418-a44a-8676a3278a6a@gentoo.org> (raw)
In-Reply-To: <6e4144f5-e69a-96ea-4ce7-717d1f85376b@gentoo.org>

On 12/4/18 5:17 PM, Kristian Fiskerstrand wrote:
> 
> Well, in terms of CVEs the documentation matters quite a bit, the
> question isn't necessarily what any user would do ... but what a
> reasonable user would do.. and a reasonable user would consider the
> documented practices of a project.
> 

There's too much crap to read. Sometimes you've just got to assume that 
a package marked "stable" on a popular distribution with a dedicated 
security team isn't going to have a 9-month-old well-known root exploit 
in the wild. That's perfectly reasonable to me.


  reply	other threads:[~2018-12-04 22:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 20:55 [gentoo-project] [pre-glep] Security Project Structure Kristian Fiskerstrand
2018-12-04 21:05 ` [gentoo-project] " Kristian Fiskerstrand
2018-12-04 22:05   ` Michael Orlitzky
2018-12-04 22:17     ` Kristian Fiskerstrand
2018-12-04 22:23       ` Michael Orlitzky [this message]
2018-12-04 22:35       ` Aaron Bauman
2018-12-04 22:30     ` Aaron Bauman
2018-12-05  9:12       ` M. J. Everitt
2018-12-05  2:36     ` Christopher Díaz Riveros
2018-12-05  3:46     ` Virgil Dupras
2018-12-05 15:02       ` Mikle Kolyada
2018-12-06 22:41   ` Alec Warner

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=1cd5f6d9-b71e-a418-a44a-8676a3278a6a@gentoo.org \
    --to=mjo@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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