From: Jiri Kosina <jkosina@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: GPZv4
Date: Tue, 17 Apr 2018 23:43:25 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1804172341130.28129@cbobk.fhfr.pm> (raw)
In-Reply-To: <e9c5d6ef-ed8f-8ad7-99ca-96a0857a2704@redhat.com>
On Tue, 17 Apr 2018, speck for Jon Masters wrote:
> The proposal would be that it only allows you to go one-way. You can say
> "I am vulnerable", turn off MD, but you can't say "I am not vulnerable".
That means we probably never reach full coverage; the problem with this
"opt-in" aproach is that noone would ever bother (even more so as time
passess) to add this explicit "I am vulnerable" call into the source; it's
basically out of control, and thus unmaintainable.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2018-04-17 21:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 18:26 [MODERATED] GPZv4 Jon Masters
2018-04-17 19:31 ` [MODERATED] GPZv4 Borislav Petkov
2018-04-17 19:56 ` Jon Masters
2018-04-17 20:37 ` Borislav Petkov
2018-04-17 21:03 ` Jon Masters
2018-04-17 21:20 ` Borislav Petkov
2018-04-17 21:22 ` GPZv4 Thomas Gleixner
2018-04-17 21:25 ` [MODERATED] GPZv4 Jiri Kosina
2018-04-17 21:38 ` Jon Masters
2018-04-17 21:43 ` Jiri Kosina [this message]
2018-04-17 22:01 ` GPZv4 Thomas Gleixner
2018-04-17 22:02 ` [MODERATED] GPZv4 Jon Masters
2018-04-18 2:48 ` Konrad Rzeszutek Wilk
2018-04-18 3:44 ` Jon Masters
2018-04-18 4:09 ` Jon Masters
2018-04-18 4:18 ` Jon Masters
2018-04-18 4:56 ` Jon Masters
2018-04-18 7:06 ` Jon Masters
2018-04-18 8:54 ` GPZv4 Thomas Gleixner
2018-04-18 13:22 ` [MODERATED] GPZv4 Jon Masters
2018-04-18 14:04 ` GPZv4 Thomas Gleixner
2018-04-18 14:07 ` [MODERATED] GPZv4 Jon Masters
2018-04-18 14:52 ` Konrad Rzeszutek Wilk
2018-04-18 15:02 ` Jon Masters
2018-04-18 21:12 ` Konrad Rzeszutek Wilk
2018-04-18 21:20 ` Jon Masters
2018-04-17 21:36 ` Jon Masters
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=nycvar.YFH.7.76.1804172341130.28129@cbobk.fhfr.pm \
--to=jkosina@suse.com \
--cc=speck@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.