9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Spectre and Meltdown
Date: Wed, 10 Jan 2018 13:30:30 -0800	[thread overview]
Message-ID: <CAJSxfm+QR2QfRc8t4OUxZEqFqccOe9DKpoTKkZo2qFbCF52CAQ@mail.gmail.com> (raw)
In-Reply-To: <dacd536d-b270-472d-81e9-1771c678c38b@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]

yep. i mentioned npm, but there are a few more.

On Wed, Jan 10, 2018 at 12:56 PM, Erik Quanstrom <quanstro@quanstro.net>
wrote:

> it is also exploitable in node.js.
>
> On Jan 10, 2018 12:52, Skip Tavakkolian <skip.tavakkolian@gmail.com>
> wrote:
>
> i think "javascript in the browser" is implied here. and that is a HUGE
> gate to close.
>
> fortunately, we don't have such browsers in plan9 :)
>
> On Wed, Jan 10, 2018 at 11:41 AM, Erik Quanstrom <quanstro@quanstro.net>
> wrote:
>
> to be fair, this vulnerability can be exploited with plain old JavaScript.
>
> On Jan 10, 2018 11:32, Skip Tavakkolian <skip.tavakkolian@gmail.com>
> wrote:
>
> good advice. i agree with the wait-and-see. i'm not convinced that this
> issue is solvable.
>
> using pip, npm and all the other ways of importing random code from
> who-knows-where is insanity and plan9 systems (mostly?) avoid this practice.
> having dedicated auth and fs servers (don't allow cpu'ing) and using
> terminals for each user is a good practice.
> a terminal on an affected processor can still compromise your factotum
> data in memory. rpi3 is a safe choice and, for plan9, probably the best
> choice.
>
>
>
> On Wed, Jan 10, 2018 at 8:59 AM, <cinap_lenrek@felloff.net> wrote:
>
> wait and see if all these scrambled together mitigations actually work.
>
> 9front is not in the business of selling shared computing environments
> (or sell executable javascript ads) to untrusted strangers.
>
> that was never really safe to begin with. there will be bugs in software
> and hardware. and there will be side channels.
>
> if you are concerned about security and leaks then run your authentication
> server on a dedicated box and applications on your own terminal.
>
> --
> cinap
>
>
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 3319 bytes --]

  reply	other threads:[~2018-01-10 21:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 16:59 cinap_lenrek
2018-01-10 19:32 ` Skip Tavakkolian
2018-01-10 19:41   ` Erik Quanstrom
2018-01-10 20:52     ` Skip Tavakkolian
2018-01-10 20:56       ` Erik Quanstrom
2018-01-10 21:30         ` Skip Tavakkolian [this message]
2018-01-10 23:46   ` Richard Miller
2018-01-11  0:33     ` Bakul Shah
2018-01-11 14:19       ` [9fans] broadpwn (was Spectre and Meltdown) Richard Miller
2018-01-11  0:55     ` [9fans] Spectre and Meltdown Skip Tavakkolian
2018-01-11  9:35       ` hiro
2018-01-11  9:49         ` Rui Carmo
2018-01-11  9:58         ` Richard Miller
2018-01-12 11:45           ` hiro
2018-01-16  0:51             ` Jules Merit
2018-01-16  1:16               ` Jules Merit
2018-01-15  9:57 ` Giacomo Tesio
  -- strict thread matches above, loose matches on Subject: below --
2018-01-15 11:26 cinap_lenrek
2018-01-10 21:43 cinap_lenrek
2018-01-10 22:46 ` Skip Tavakkolian
2018-01-10 22:48 ` Charles Forsyth
2018-01-10 20:30 cinap_lenrek
2018-01-10 20:41 ` Erik Quanstrom
2018-01-10 20:48 ` Skip Tavakkolian
     [not found] <1911496352.319586.1515073776091.ref@mail.yahoo.com>
2018-01-04 13:49 ` G B
     [not found]   ` <CAJSxfmJ18xgD1thWvT80=o321-qKCEfecYb37gaFyC=CApWvmg@mail.gmail.com>
     [not found]     ` <CAJSxfmKsqOZVpcGmqEK3ar=h0-z8qn0GvYy_JNH_8x2OztMXrw@mail.gmail.com>
2018-01-10 16:27       ` Skip Tavakkolian

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=CAJSxfm+QR2QfRc8t4OUxZEqFqccOe9DKpoTKkZo2qFbCF52CAQ@mail.gmail.com \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).