From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Guidelines for dangerous USE flags
Date: Tue, 29 Aug 2017 10:21:28 +0000 (UTC) [thread overview]
Message-ID: <pan$b2c1b$a5c3d588$9808626a$30020d4f@cox.net> (raw)
In-Reply-To: 20170829211332.61f19e10@katipo2.lan
Kent Fredric posted on Tue, 29 Aug 2017 21:21:09 +1200 as excerpted:
> On Thu, 24 Aug 2017 03:06:13 +0000 (UTC)
> Duncan <1i5t5.duncan@cox.net> wrote:
>
>> nrpe-command-args-SECURITY-HOLE or just nrpe-GAPING-SECURITY-HOLE
>
> That's probably excessive, if you set that USE flag globally, you
> deserve what you get.
>
> And if you are responsible and you know what you're getting, then you
> should be allowed to do that ( even though I struggle to understand why
> )
Good point.
(And the global-use "why" might conceivably be creating a deliberate
multiple-vulnerability distro for people to test their exploit abilities
and techniques on, like the one I remember reading about awhile back.
Unfortunately IDR the name, but someone will likely reply with it...)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-08-29 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 17:22 [gentoo-dev] Guidelines for dangerous USE flags Michael Orlitzky
2017-08-22 17:37 ` Sven Vermeulen
2017-08-24 3:06 ` [gentoo-dev] " Duncan
2017-08-29 9:21 ` Kent Fredric
2017-08-29 10:21 ` Duncan [this message]
2017-08-22 18:44 ` [gentoo-dev] " Robin H. Johnson
2017-08-24 15:22 ` Michael Orlitzky
2017-08-25 22:07 ` William Hubbs
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='pan$b2c1b$a5c3d588$9808626a$30020d4f@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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