general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: "infokiller ." <joweill@icloud.com>
To: discuss@spectrum-os.org
Subject: High level design and other related projects
Date: Fri, 12 Jun 2020 11:16:11 -0000	[thread overview]
Message-ID: <159196057136.15924.4785359159629836782@localhost> (raw)

Apologies for the incoherent title: I'd like to better understand the design choices of this project and discuss how it relates to other projects in this space.
First I'd like to say that I think that using crosvm is a really great decision. Google has a lot of manpower working on ChromeOS and Android, and building on their work is something that should
pay off, especially for a project such as Spectrum that tackles such a huge undertaking (building a secure OS).

Here's a few questions to kick off the discussion:

- Have you considered using a micro kernel based host like seL4, similar to what Genode does (at least as I understand it)?
- Have you considered gVisor [1] for lightweight compartmentalization?
- Have you considered reusing stuff from the Whonix project?

## References

[1] https://github.com/google/gvisor

             reply	other threads:[~2020-06-12 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 11:16 infokiller . [this message]
2020-06-13 12:01 ` Alyssa Ross
2020-06-14 20:24   ` infokiller ​

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=159196057136.15924.4785359159629836782@localhost \
    --to=joweill@icloud.com \
    --cc=discuss@spectrum-os.org \
    /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).