From 6aa5c68d8252789482a0b475f34b0623c7990fbe Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Wed, 16 Dec 2020 23:06:00 -0500 Subject: move roadmap to FAQ --- static/index.html | 30 ++---------------------------- 1 file changed, 2 insertions(+), 28 deletions(-) (limited to 'static/index.html') diff --git a/static/index.html b/static/index.html index c32032f3..440a9947 100644 --- a/static/index.html +++ b/static/index.html @@ -25,7 +25,7 @@ - +

@@ -223,33 +223,7 @@

Roadmap

To get an idea of the near term roadmap, check out the - issue trackers. The vast majority of the - issues filed in the trackers are planned enhancements, with care taken to make sure - all of the issues open in the tracker are concrete and actionable.

In the long term, GrapheneOS aims to move beyond a hardened fork of the Android - Open Source Project. Achieving the goals requires moving away from relying on the Linux - kernel as the core of the OS and foundation of the security model. It needs to move - towards a microkernel-based model with a Linux compatibility layer, with many stepping - stones leading towards that goal including adopting virtualization-based - isolation.

The initial phase for the long-term roadmap of moving away from the current - foundation will be to deploy and integrate a hypervisor like Xen to leverage it for - reinforcing existing security boundaries. Linux would be running inside the virtual - machines at this point, inside and outside of the sandboxes being reinforced. In the - longer term, Linux inside the sandboxes can be replaced with a compatibility layer - like gVisor, which would need to be ported to arm64 and given a new backend alongside - the existing KVM backend. Over the longer term, i.e. many years from now, Linux can - fade away completely and so can the usage of virtualization. The anticipation is that - many other projects are going to be interested in this kind of migration, so it's not - going to be solely a GrapheneOS project, as demonstrated by the current existence of - the gVisor project and various other projects working on virtualization deployments - for mobile. Having a hypervisor with verified boot still intact will also provide a - way to achieve some of the goals based on extensions to Trusted Execution Environment - (TEE) functionality even without having GrapheneOS hardware.

Hardware and firmware security are core parts of the project, but it's currently - limited to research and submitting suggestions and bug reports upstream. In the long - term, the project will need to move into the hardware space.

See the FAQ section on the roadmap.

-- cgit v1.3.1