All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH SSBv11 0/3] seccomp 1
Date: Thu, 3 May 2018 07:47:04 -0700	[thread overview]
Message-ID: <20180503144704.GW75137@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805031438330.1672@nanos.tec.linutronix.de>

> Telling people: "We have this shiny new prtcl and your browser will
> eventually use it but until then you're on your own." is just bullshit.

No the browsers will not need to use the prctl. 

The browser will turn on process site isolation (e.g. in Chrome it is already
a config option) then it doesn't need the prctl because leaking data
inside a process doesn't matter.

And the browsers were actually the main target for this. But if they
don't need it it doesn't make that much sense frankly.

For many other programs it is actually awkward to use because they haven't
been enabled for seccomp yet. For those the plain prctl is better.

So essentially you just slow down the browsers for no gain.

-Andi

      parent reply	other threads:[~2018-05-03 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  0:44 [MODERATED] [PATCH SSBv11 0/3] seccomp 1 Kees Cook
2018-05-01 22:07 ` [MODERATED] [PATCH SSBv11 3/3] seccomp 0 Kees Cook
2018-05-01 22:19 ` [MODERATED] [PATCH SSBv11 1/3] seccomp 2 Kees Cook
2018-05-01 22:31 ` [MODERATED] [PATCH SSBv11 2/3] seccomp 3 Kees Cook
2018-05-03  8:58 ` [MODERATED] Re: [PATCH SSBv11 3/3] seccomp 0 Peter Zijlstra
2018-05-03  9:21   ` Thomas Gleixner
2018-05-03 16:03     ` [MODERATED] " Kees Cook
2018-05-03 12:29 ` [MODERATED] Re: [PATCH SSBv11 0/3] seccomp 1 Andi Kleen
2018-05-03 12:45   ` Thomas Gleixner
2018-05-03 14:09     ` [MODERATED] " Ingo Molnar
2018-05-03 14:57       ` Andi Kleen
2018-05-03 17:04       ` Kees Cook
2018-05-03 18:58         ` Andi Kleen
2018-05-03 23:17           ` Kees Cook
2018-05-03 14:47     ` Andi Kleen [this message]

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=20180503144704.GW75137@tassilo.jf.intel.com \
    --to=ak@linux.intel.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.