From: Bakul Shah <bakul@bitblocks.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 16:33:43 -0800 [thread overview]
Message-ID: <20180111003358.4AFE6156E524@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 10 Jan 2018 23:46:47 +0000." <cb16e3ce22901b9ee1b6cb654f9bbee8@hamnavoe.com>
On Wed, 10 Jan 2018 23:46:47 +0000 Richard Miller <9fans@hamnavoe.com> wrote:
Richard Miller writes:
> > rpi3 is a safe choice
>
> Safe against spectre perhaps, but there are interesting remote attacks
> against the firmware in the bcm43xx wifi engine. I wouldn't want to bet
> on plan 9's immunity to some variant of broadpwn.
CVE-2017-9417. Poking around the 'net I found
https://github.com/raspberrypi/linux/issues/1342#issuecomment-321221748
Need Linux to run this but does not fix the problem?
Though there seems to be another unrelated problem that seems
not quite fixed.
next prev parent reply other threads:[~2018-01-11 0:33 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
2018-01-10 23:46 ` Richard Miller
2018-01-11 0:33 ` Bakul Shah [this message]
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=20180111003358.4AFE6156E524@mail.bitblocks.com \
--to=bakul@bitblocks.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).