From: Alyssa Ross <hi@alyssa.is>
To: devel@spectrum-os.org
Cc: Molly Miller <mm@m-squa.red>, Michael Raskin <7c6f434c@mail.ru>
Subject: [PATCH www 2/1] design.html: mention aarch64 as well as x86_64
Date: Sat, 21 Nov 2020 15:23:14 +0000 [thread overview]
Message-ID: <20201121152314.15152-1-hi@alyssa.is> (raw)
In-Reply-To: <20201118120116.21390-1-hi@alyssa.is>
Michael is right that aarch64 is probably suitably performant at this
point.
I also improved the arguments here a bit as it was lacking before.
For example, the "huge attack surface" (of the Management Engine) link
pointed to a talk that wasn't about the ME at all, but about a
backdoor in VIA's instruction set.
Cc: Michael Raskin <7c6f434c@mail.ru>
---
I'd like to continue to link to x86 Considered Harmful somewhere in
the text, but couldn't figure out how to fit it in since there's not
really anywhere I'm talking about x86 specifically rather than all
architectures. I'd appreciate suggestions for how I might do that.
design.html | 47 +++++++++++++++++++++++++++++------------------
1 file changed, 29 insertions(+), 18 deletions(-)
diff --git a/design.html b/design.html
index f683ed4..3c0e37d 100644
--- a/design.html
+++ b/design.html
@@ -113,19 +113,28 @@ configuration file. This use case should be kept in mind when writing
the Nix API for Spectrum.
<p>
-While Spectrum is expected to largely run on personal computers, most
-of which will almost certainly use the x86_64 architecture, this will
-not be the only architecture given first class support by Spectrum.
-One of the advantages to Spectrum's Linux base is the extremely wide
-hardware support that Linux offers, and, beyond that, x86_64
-is <a href="https://blog.invisiblethings.org/papers/2015/x86_harmful.pdf">notably
-untrustworthy</a>, especially with
-the <a href="https://invidio.us/watch?v=_eSAF_qT_FY">huge attack
-surface</a> of
-the <a href="https://en.wikipedia.org/wiki/Intel_Management_Engine">Intel
-Management Engine</a>
-/ <a href="https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor">AMD
-Platform Security Processor</a>.
+Spectrum is expected to largely run on personal computers, most of
+which will almost certainly use the x86_64 or aarch64 architectures.
+Unfortunately, these common architectures are the most lacking in
+terms of trustworthiness. All require unauditable proprietary blogs
+to boot, and
+the <a href="https://en.wikipedia.org/wiki/Intel_Management_Engine">Intel
+Management
+Engine</a>, <a href="https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor">AMD
+Platform Security Processer</a>,
+and <a href="https://en.wikipedia.org/wiki/ARM_architecture#Security_extensions">ARM
+TrustZone</a>, all of which are constantly running highly privileged,
+unauditable code. A backdoor or compromise in any of this code could
+give complete access to the system, invisibly to running the operating
+system. As more functionality is moved into these environments, the
+attack surfaces grow larger and larger, and
+already <a href="https://en.wikipedia.org/wiki/Intel_Management_Engine#Security_vulnerabilities">many
+vulnerabilities</a> have been demonstrated in the most studied of
+these systems, Intel's Management Engine. Fears of backdoors are not
+unjustified either — VIA C3 x86 CPUs used in personal computers have
+been found to contain
+a <a href="https://i.blackhat.com/us-18/Thu-August-9/us-18-Domas-God-Mode-Unlocked-Hardware-Backdoors-In-x86-CPUs-wp.pdf">hardware
+backdoor</a> allowing local privilege escalation.
<p>
I would like Spectrum to additionally have first class support for at
@@ -133,13 +142,15 @@ least ppc64le. This is the only other architecture that can come
close to the sheer performance x86_64 can offer at the high end, and
in stark contrast to x86_64, it is possible to buy a new ppc64le
(POWER9) system that does not require any proprietary firmware that
-cannot be inspected and audited. A blocker for POWER9 support is an
-support in crosvm for virtualizing that architecture, which is outside
-the expertise of anybody currently working on Spectrum but would be a
-very welcome contribution.
+cannot be inspected and audited. One of the advantages of Spectrum's
+Linux base is the extremely wide hardware support that Linux offers,
+so the only blocker for POWER9 support is support in crosvm for
+virtualizing that architecture, which is outside the expertise of
+anybody currently working on Spectrum but would be a very welcome
+contribution.
<p>
-Ideally, all Spectrum packages, x86_64 and ppc64le, would be built on
+Ideally, all Spectrum packages, for all architectures, would be built on
POWER9 hardware. Even if a user has to trust the x86_64 computer
available to them, anti-freedom firmware, undocumented backdoors and
all, they would be able to benefit from binary packages that were
--
2.27.0
next prev parent reply other threads:[~2020-11-21 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:01 [PATCH www] design.html: backpedal a bit on POWER9 Alyssa Ross
2020-11-18 12:52 ` Michael Raskin
2020-11-20 14:06 ` Alyssa Ross
2020-11-21 15:23 ` Alyssa Ross [this message]
2020-11-21 16:34 ` [PATCH www 2/1] design.html: mention aarch64 as well as x86_64 Michael Raskin
2020-11-22 20:09 ` Alyssa Ross
2020-11-29 23:54 ` [PATCH www 3/1] design.html: mention goal of diverse build hardware Alyssa Ross
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=20201121152314.15152-1-hi@alyssa.is \
--to=hi@alyssa.is \
--cc=7c6f434c@mail.ru \
--cc=devel@spectrum-os.org \
--cc=mm@m-squa.red \
/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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).